Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9504d1221e4bd6fbb4266160962bd27455fc978f6ec23e1dc2f068705b78e38

Tx prefix hash: 431f176324d8fc51121304d46a5b200582f0f68b7b99476e47fff7403e2df831
Tx public key: dcc2409ecc71cccb72b6f6e2be95d88c6b1a2f98d9845a737d5a134e951bff86
Timestamp: 1700823939 Timestamp [UCT]: 2023-11-24 11:05:39 Age [y:d:h:m:s]: 01:160:21:24:52
Block: 898566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376188 RingCT/type: yes/0
Extra: 01dcc2409ecc71cccb72b6f6e2be95d88c6b1a2f98d9845a737d5a134e951bff86021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.646662706000 dcy

stealth address amount amount idx
00: 7b7bc18aabb286ed0fd4165a0afa88e1d4a22d58a9718a9af6eccb17dede90c7 0.646662706000 1354987 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": 898576, "vin": [ { "gen": { "height": 898566 } } ], "vout": [ { "amount": 646662706, "target": { "key": "7b7bc18aabb286ed0fd4165a0afa88e1d4a22d58a9718a9af6eccb17dede90c7" } } ], "extra": [ 1, 220, 194, 64, 158, 204, 113, 204, 203, 114, 182, 246, 226, 190, 149, 216, 140, 107, 26, 47, 152, 217, 132, 90, 115, 125, 90, 19, 78, 149, 27, 255, 134, 2, 17, 0, 0, 0, 6, 230, 210, 127, 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