Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bf5eb8e13f5e0b3d73c7d66c6c7d6f93933f4c9f74d946d0a29d81f4324cb57d

Tx prefix hash: 3b620ed9b97cf595ec7f77dbdae0b4c1eeef7e846b259bcc4d3dfc8c81bf9950
Tx public key: 9a77042856e0c1830e16bf2b8257236e4bb0000d7ce8a4192ee5e2ce024cfaf1
Timestamp: 1735962991 Timestamp [UCT]: 2025-01-04 03:56:31 Age [y:d:h:m:s]: 00:304:03:41:41
Block: 1189767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214876 RingCT/type: yes/0
Extra: 019a77042856e0c1830e16bf2b8257236e4bb0000d7ce8a4192ee5e2ce024cfaf10211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e5c3c52474e3597fcd502eb590367ad08ef4f62a7bc726fe808d74cd7c6e57f 0.600000000000 1676278 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1189777, "vin": [ { "gen": { "height": 1189767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e5c3c52474e3597fcd502eb590367ad08ef4f62a7bc726fe808d74cd7c6e57f" } } ], "extra": [ 1, 154, 119, 4, 40, 86, 224, 193, 131, 14, 22, 191, 43, 130, 87, 35, 110, 75, 176, 0, 13, 124, 232, 164, 25, 46, 229, 226, 206, 2, 76, 250, 241, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8