Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59a0776a8c704117f787482cd82b29828d58efa56184e790bd67506817ffd353

Tx prefix hash: 4015b09d2561dda527f9f14f0d2450d0ca7c8ec087540784e682c66880c84011
Tx public key: e214a1c1df41db50233e0e7e32e04d9901b60f4a1242d6b50548c1c9cee4e1e8
Timestamp: 1579542287 Timestamp [UCT]: 2020-01-20 17:44:47 Age [y:d:h:m:s]: 04:170:10:43:51
Block: 49572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1011407 RingCT/type: yes/0
Extra: 01e214a1c1df41db50233e0e7e32e04d9901b60f4a1242d6b50548c1c9cee4e1e8021100000021d81c26c0000000000000000000

1 output(s) for total of 420.482784284000 dcy

stealth address amount amount idx
00: bd553df199783a7f2df98d3f0a1ea3912c8ceaaf4d5c895d274f16e6998a97b2 420.482784284000 92084 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": 49582, "vin": [ { "gen": { "height": 49572 } } ], "vout": [ { "amount": 420482784284, "target": { "key": "bd553df199783a7f2df98d3f0a1ea3912c8ceaaf4d5c895d274f16e6998a97b2" } } ], "extra": [ 1, 226, 20, 161, 193, 223, 65, 219, 80, 35, 62, 14, 126, 50, 224, 77, 153, 1, 182, 15, 74, 18, 66, 214, 181, 5, 72, 193, 201, 206, 228, 225, 232, 2, 17, 0, 0, 0, 33, 216, 28, 38, 192, 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