Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ab911debfe043a2e1aa29c418cb10d72c0fe85feb419a8ec1b0e4b1828a288

Tx prefix hash: d3ed59aeb5a3bcd9cd8e23e320285d8fe7476abe4ed4bad44ba1ebb5923a2c29
Tx public key: 4ea3ef7628a3265333f4fa086545161f951332df9b555b20c62ecaf17eee8593
Timestamp: 1716582132 Timestamp [UCT]: 2024-05-24 20:22:12 Age [y:d:h:m:s]: 00:298:18:50:16
Block: 1029222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213557 RingCT/type: yes/0
Extra: 014ea3ef7628a3265333f4fa086545161f951332df9b555b20c62ecaf17eee85930211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc8722a0bd3e112a7a4343f7f44a50f28509c14e1cced89d9cae93b5b2c28451 0.600000000000 1497253 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": 1029232, "vin": [ { "gen": { "height": 1029222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc8722a0bd3e112a7a4343f7f44a50f28509c14e1cced89d9cae93b5b2c28451" } } ], "extra": [ 1, 78, 163, 239, 118, 40, 163, 38, 83, 51, 244, 250, 8, 101, 69, 22, 31, 149, 19, 50, 223, 155, 85, 91, 32, 198, 46, 202, 241, 126, 238, 133, 147, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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