Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 994f5c17fb7c141c8ec6ca4c5a0f80d9b5bdc637d7826cc63e6dc25ef87a3e86

Tx prefix hash: c67c06e8fb451ba8bfa584d31f19462bf2cd5350c309ae925b41755b7b85c102
Tx public key: 476535d20b05c9e6188959d747e07e823101feada1e8222fc639be649ff6606b
Timestamp: 1715489092 Timestamp [UCT]: 2024-05-12 04:44:52 Age [y:d:h:m:s]: 01:181:07:52:01
Block: 1020193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388176 RingCT/type: yes/0
Extra: 01476535d20b05c9e6188959d747e07e823101feada1e8222fc639be649ff6606b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d7a247f5a8d5a703929687a27f576d5f36ca4b7a28e7261601619b2d79ce66e 0.600000000000 1484254 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": 1020203, "vin": [ { "gen": { "height": 1020193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d7a247f5a8d5a703929687a27f576d5f36ca4b7a28e7261601619b2d79ce66e" } } ], "extra": [ 1, 71, 101, 53, 210, 11, 5, 201, 230, 24, 137, 89, 215, 71, 224, 126, 130, 49, 1, 254, 173, 161, 232, 34, 47, 198, 57, 190, 100, 159, 246, 96, 107, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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