Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e35dfef7a73a9969fc81034f1e5218fdbe1852d2a45c9308a47957bd45dfb85a

Tx prefix hash: edd8e18709a8603b77b40e3cc78f98231812f56a51ae67fd8c120a15db35f26c
Tx public key: c858bd26511995bd74c3694a18d75bd3b61717f409ca53b0fa4e00ccc4af07f2
Timestamp: 1736199711 Timestamp [UCT]: 2025-01-06 21:41:51 Age [y:d:h:m:s]: 00:083:23:11:46
Block: 1191715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59795 RingCT/type: yes/0
Extra: 01c858bd26511995bd74c3694a18d75bd3b61717f409ca53b0fa4e00ccc4af07f2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d536273f25df6073bb0ae03da0aa28f63cc2e9cb1f89d7d2c423b39fe37970b1 0.600000000000 1678256 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": 1191725, "vin": [ { "gen": { "height": 1191715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d536273f25df6073bb0ae03da0aa28f63cc2e9cb1f89d7d2c423b39fe37970b1" } } ], "extra": [ 1, 200, 88, 189, 38, 81, 25, 149, 189, 116, 195, 105, 74, 24, 215, 91, 211, 182, 23, 23, 244, 9, 202, 83, 176, 250, 78, 0, 204, 196, 175, 7, 242, 2, 17, 0, 0, 0, 1, 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