Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efa25e79279d72cccec89bc88141594cab80c11e2b372e44a2e496f6a4a30598

Tx prefix hash: a9f67376361e764d15d804e30586791907c85f5ff466f7e9f324f23f52d6b3d4
Tx public key: 6463de5a9a486f6924bf97c26f2f738a40389fcb2e7be34e9c63a9f17d5caebd
Timestamp: 1725194917 Timestamp [UCT]: 2024-09-01 12:48:37 Age [y:d:h:m:s]: 00:212:14:16:42
Block: 1100627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151771 RingCT/type: yes/0
Extra: 016463de5a9a486f6924bf97c26f2f738a40389fcb2e7be34e9c63a9f17d5caebd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fa464e456f7a5526fd7c7fdad99ac1e58f3418687fd7986597364de9dcb99a1 0.600000000000 1576606 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": 1100637, "vin": [ { "gen": { "height": 1100627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fa464e456f7a5526fd7c7fdad99ac1e58f3418687fd7986597364de9dcb99a1" } } ], "extra": [ 1, 100, 99, 222, 90, 154, 72, 111, 105, 36, 191, 151, 194, 111, 47, 115, 138, 64, 56, 159, 203, 46, 123, 227, 78, 156, 99, 169, 241, 125, 92, 174, 189, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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