Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25f0fd5618de654302b787e7890fd7a0b0b802c1855bce920cc8f3466d56583

Tx prefix hash: a49aeafddeaaa145f52f89990cc7703a73e77564ea7e13b252741574be92c0ff
Tx public key: fb0bdce5cb69b724e61dbee6d9f975a273284088d19a0e851259f0666844a3ea
Timestamp: 1708451769 Timestamp [UCT]: 2024-02-20 17:56:09 Age [y:d:h:m:s]: 01:261:01:40:15
Block: 961811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445330 RingCT/type: yes/0
Extra: 01fb0bdce5cb69b724e61dbee6d9f975a273284088d19a0e851259f0666844a3ea0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f80ee45396e3ddc79d8702ae84c548bc551553773ed37290c36c7d850a93dcc3 0.600000000000 1421424 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": 961821, "vin": [ { "gen": { "height": 961811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f80ee45396e3ddc79d8702ae84c548bc551553773ed37290c36c7d850a93dcc3" } } ], "extra": [ 1, 251, 11, 220, 229, 203, 105, 183, 36, 230, 29, 190, 230, 217, 249, 117, 162, 115, 40, 64, 136, 209, 154, 14, 133, 18, 89, 240, 102, 104, 68, 163, 234, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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