Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 776ce81dc59834b9de80cc20020fe77bfc1ded232f7c65675ac42773519a81e2

Tx prefix hash: 0dc95c29253ad829d9d28b998172ef33e90cc08f7aa65a41d97899e6d9bda017
Tx public key: e45d06c51c52b4aa0ce233d0b12bcfc4f8a9a593e412846bbb6ba0244a8e2afb
Timestamp: 1708721530 Timestamp [UCT]: 2024-02-23 20:52:10 Age [y:d:h:m:s]: 00:336:02:27:08
Block: 964054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240548 RingCT/type: yes/0
Extra: 01e45d06c51c52b4aa0ce233d0b12bcfc4f8a9a593e412846bbb6ba0244a8e2afb02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00d762c2cefa1016d39180e577b14778058fc849c6cf2ed83051acabfd3ff5b9 0.600000000000 1423781 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": 964064, "vin": [ { "gen": { "height": 964054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00d762c2cefa1016d39180e577b14778058fc849c6cf2ed83051acabfd3ff5b9" } } ], "extra": [ 1, 228, 93, 6, 197, 28, 82, 180, 170, 12, 226, 51, 208, 177, 43, 207, 196, 248, 169, 165, 147, 228, 18, 132, 107, 187, 107, 160, 36, 74, 142, 42, 251, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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