Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 370ba19fef9051b0661f8533f57f90c590c12070161400db7e1888bc2af2a24c

Tx prefix hash: ad85e837bb3d639456c1591468bd866c2cd8542322e2b7886b22cf63b4898e74
Tx public key: e5c52e2df153d936ed164db603e33690da5f6646697d9f6b77a415bead7a1fd4
Timestamp: 1634639320 Timestamp [UCT]: 2021-10-19 10:28:40 Age [y:d:h:m:s]: 02:226:15:38:21
Block: 356117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 679007 RingCT/type: yes/0
Extra: 01e5c52e2df153d936ed164db603e33690da5f6646697d9f6b77a415bead7a1fd40211000000c8f29d7abf000000000000000000

1 output(s) for total of 40.554304940000 dcy

stealth address amount amount idx
00: 0b0f5007e5b8998748e074522bd146c3d909703c75de4e8f2cadc744e32d3c0d 40.554304940000 726727 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": 356127, "vin": [ { "gen": { "height": 356117 } } ], "vout": [ { "amount": 40554304940, "target": { "key": "0b0f5007e5b8998748e074522bd146c3d909703c75de4e8f2cadc744e32d3c0d" } } ], "extra": [ 1, 229, 197, 46, 45, 241, 83, 217, 54, 237, 22, 77, 182, 3, 227, 54, 144, 218, 95, 102, 70, 105, 125, 159, 107, 119, 164, 21, 190, 173, 122, 31, 212, 2, 17, 0, 0, 0, 200, 242, 157, 122, 191, 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