Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a35ef6130279afb49563ac9a1a6b14c0e0ef9ab77992154b14b2bbf75be2bed

Tx prefix hash: e6404fd71a3cf945d1e3b366093c9a1799a5e3928bb6aa082ba117519a0d9225
Tx public key: a5e18543bd28e2998bcadd1471a87b16f2c1b2e88a0fc57aabe2d0666bdcf7fb
Timestamp: 1725681951 Timestamp [UCT]: 2024-09-07 04:05:51 Age [y:d:h:m:s]: 00:214:23:19:54
Block: 1104658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153491 RingCT/type: yes/0
Extra: 01a5e18543bd28e2998bcadd1471a87b16f2c1b2e88a0fc57aabe2d0666bdcf7fb02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f632c09f518cf4d49325173947bd919756444df1743640e80d64a2d5d559635e 0.600000000000 1581883 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": 1104668, "vin": [ { "gen": { "height": 1104658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f632c09f518cf4d49325173947bd919756444df1743640e80d64a2d5d559635e" } } ], "extra": [ 1, 165, 225, 133, 67, 189, 40, 226, 153, 139, 202, 221, 20, 113, 168, 123, 22, 242, 193, 178, 232, 138, 15, 197, 122, 171, 226, 208, 102, 107, 220, 247, 251, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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