Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d1c1da012ab3981eaee6566db91afc28bceb9595d669c3b496a0ce0cbfbf01e

Tx prefix hash: cf2e69f5d7d5bd770e598095e4312382a3e4a82c9828fcb39bdf0741a67de30d
Tx public key: d100261cebaa308015bca129254fdf37678c6e83c7b70a4169fe49b8303a2414
Timestamp: 1700854248 Timestamp [UCT]: 2023-11-24 19:30:48 Age [y:d:h:m:s]: 00:336:16:55:01
Block: 898832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241141 RingCT/type: yes/0
Extra: 01d100261cebaa308015bca129254fdf37678c6e83c7b70a4169fe49b8303a2414021100000008faf35c9c000000000000000000

1 output(s) for total of 0.645351682000 dcy

stealth address amount amount idx
00: 639ee6d35f9598ad97263ce313f72d89c46f30a9f0af44bfa8a57b48daf979b2 0.645351682000 1355267 of 0

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": 898842, "vin": [ { "gen": { "height": 898832 } } ], "vout": [ { "amount": 645351682, "target": { "key": "639ee6d35f9598ad97263ce313f72d89c46f30a9f0af44bfa8a57b48daf979b2" } } ], "extra": [ 1, 209, 0, 38, 28, 235, 170, 48, 128, 21, 188, 161, 41, 37, 79, 223, 55, 103, 140, 110, 131, 199, 183, 10, 65, 105, 254, 73, 184, 48, 58, 36, 20, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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