Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ce993df9557b95a734f23d0ce1cc78a25635a2b77923f9e22aaee38552d74ae

Tx prefix hash: 39a25982811a402c87562d30637dda57981c0957aa229eaa63de62287cbf2427
Tx public key: 24610855d841d30e1aee939c85c51111da8a86eee469d0aa2546d2ce4aa1a883
Timestamp: 1716477616 Timestamp [UCT]: 2024-05-23 15:20:16 Age [y:d:h:m:s]: 00:320:23:15:32
Block: 1028356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229409 RingCT/type: yes/0
Extra: 0124610855d841d30e1aee939c85c51111da8a86eee469d0aa2546d2ce4aa1a88302110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb8de72d56f8e21796fd72c96ebd9cb4decc542bf5bbfffbf30deab248af2b2 0.600000000000 1496347 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": 1028366, "vin": [ { "gen": { "height": 1028356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb8de72d56f8e21796fd72c96ebd9cb4decc542bf5bbfffbf30deab248af2b2" } } ], "extra": [ 1, 36, 97, 8, 85, 216, 65, 211, 14, 26, 238, 147, 156, 133, 197, 17, 17, 218, 138, 134, 238, 228, 105, 208, 170, 37, 70, 210, 206, 74, 161, 168, 131, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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