Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b641dbfa7866e88976f84cc698fdd047c6f041517b89bddd77a426398dd4a9d

Tx prefix hash: 3a345f284c151eb47d3aa5c3954e8a35bc0432fa5d9f838c742134c44c61252e
Tx public key: b06661564c703ddd1dc1cb272d298ab333d58b5df6887c076c388e00b7e94c58
Timestamp: 1740809173 Timestamp [UCT]: 2025-03-01 06:06:13 Age [y:d:h:m:s]: 00:265:15:11:01
Block: 1229604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187610 RingCT/type: yes/0
Extra: 01b06661564c703ddd1dc1cb272d298ab333d58b5df6887c076c388e00b7e94c58021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a62476f0bdf8fe9c16324f451cb0edb03f87e8d61ecdd1073f1737c685c096d3 0.600000000000 1716491 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": 1229614, "vin": [ { "gen": { "height": 1229604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a62476f0bdf8fe9c16324f451cb0edb03f87e8d61ecdd1073f1737c685c096d3" } } ], "extra": [ 1, 176, 102, 97, 86, 76, 112, 61, 221, 29, 193, 203, 39, 45, 41, 138, 179, 51, 213, 139, 93, 246, 136, 124, 7, 108, 56, 142, 0, 183, 233, 76, 88, 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