Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6987c1d561933afff814bb636dda354c72d4b87b379d4ea1763bea08e61a5d1

Tx prefix hash: 3e9fad4f3d693247c6ad966648bbaafe0115a3586621f8d39cf7ead02a9b5cb3
Tx public key: d13cf0006595a1517aa58f703e61962343c6cde9727240d36e718bb94d5e242c
Timestamp: 1726633379 Timestamp [UCT]: 2024-09-18 04:22:59 Age [y:d:h:m:s]: 00:273:02:16:31
Block: 1112542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194929 RingCT/type: yes/0
Extra: 01d13cf0006595a1517aa58f703e61962343c6cde9727240d36e718bb94d5e242c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd3f7d154ee5f05db40c0ec4d23f322b811ef574af2d553897dddeed3d070b49 0.600000000000 1591901 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": 1112552, "vin": [ { "gen": { "height": 1112542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd3f7d154ee5f05db40c0ec4d23f322b811ef574af2d553897dddeed3d070b49" } } ], "extra": [ 1, 209, 60, 240, 0, 101, 149, 161, 81, 122, 165, 143, 112, 62, 97, 150, 35, 67, 198, 205, 233, 114, 114, 64, 211, 110, 113, 139, 185, 77, 94, 36, 44, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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