Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beac83b0f183e6d7109a1502ed0c9369609902a4526a44a1774d966fb5fed29c

Tx prefix hash: df6f0bea716a7863c98b4bea11a41c61b2a6721797de479b8594c12fa66072e5
Tx public key: ea0c05f7206bc5a1a6e8b85647106c798f8376b15a50f5b10346839372d0f069
Timestamp: 1639245318 Timestamp [UCT]: 2021-12-11 17:55:18 Age [y:d:h:m:s]: 03:136:18:52:07
Block: 393347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 876533 RingCT/type: yes/0
Extra: 01ea0c05f7206bc5a1a6e8b85647106c798f8376b15a50f5b10346839372d0f069021100000001408d5ef5000000000000000000

1 output(s) for total of 30.526601971000 dcy

stealth address amount amount idx
00: 21f17fb46588bf07d625f55de767323657ab0f37cb156a0de6dbf639b294b17f 30.526601971000 790562 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": 393357, "vin": [ { "gen": { "height": 393347 } } ], "vout": [ { "amount": 30526601971, "target": { "key": "21f17fb46588bf07d625f55de767323657ab0f37cb156a0de6dbf639b294b17f" } } ], "extra": [ 1, 234, 12, 5, 247, 32, 107, 197, 161, 166, 232, 184, 86, 71, 16, 108, 121, 143, 131, 118, 177, 90, 80, 245, 177, 3, 70, 131, 147, 114, 208, 240, 105, 2, 17, 0, 0, 0, 1, 64, 141, 94, 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