Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c4f64113760157060a0a8605fd6748c498dc29598537fb1b53cb23f7a6f749

Tx prefix hash: bf425f754da9f5db6eec87235a587831ec77847c26d5502bee993e6da8be292b
Tx public key: 773a64c42bd515b3a14f6d19e465319978bc849b18ea5bf94ed3bb3bb938ed38
Timestamp: 1697069003 Timestamp [UCT]: 2023-10-12 00:03:23 Age [y:d:h:m:s]: 01:096:22:49:16
Block: 867652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330539 RingCT/type: yes/0
Extra: 01773a64c42bd515b3a14f6d19e465319978bc849b18ea5bf94ed3bb3bb938ed380211000000034b8f5122000000000000000000

1 output(s) for total of 0.818669810000 dcy

stealth address amount amount idx
00: 324cab39884b103e1b3fecc450f8234e4b9925ec610e5f5ad3f7a7581d01294d 0.818669810000 1322356 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": 867662, "vin": [ { "gen": { "height": 867652 } } ], "vout": [ { "amount": 818669810, "target": { "key": "324cab39884b103e1b3fecc450f8234e4b9925ec610e5f5ad3f7a7581d01294d" } } ], "extra": [ 1, 119, 58, 100, 196, 43, 213, 21, 179, 161, 79, 109, 25, 228, 101, 49, 153, 120, 188, 132, 155, 24, 234, 91, 249, 78, 211, 187, 59, 185, 56, 237, 56, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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