Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e51e8419f3c91c08853f8081d4b74c663e8f48d9320faba7c35cb8b740d0380

Tx prefix hash: aadf1a72ee14cf70395c489f98ee0930f8f7ac2c71bbe25a128c208851b4a7da
Tx public key: bfd2ada8d8eb690d1568385471faaa475b75c8f29fdd37aac5a9d2f070ee3059
Timestamp: 1734228616 Timestamp [UCT]: 2024-12-15 02:10:16 Age [y:d:h:m:s]: 00:109:10:41:17
Block: 1175433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77984 RingCT/type: yes/0
Extra: 01bfd2ada8d8eb690d1568385471faaa475b75c8f29fdd37aac5a9d2f070ee3059021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eaa29fc54a77cd72884d91aee926389a264b3317e4b7261cebf9b67a211d06b 0.600000000000 1661712 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": 1175443, "vin": [ { "gen": { "height": 1175433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eaa29fc54a77cd72884d91aee926389a264b3317e4b7261cebf9b67a211d06b" } } ], "extra": [ 1, 191, 210, 173, 168, 216, 235, 105, 13, 21, 104, 56, 84, 113, 250, 170, 71, 91, 117, 200, 242, 159, 221, 55, 170, 197, 169, 210, 240, 112, 238, 48, 89, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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