Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 368d4a25eb66f8568d1b6f43ea6d93a98273cbe9f4c714a41d3bb573fab0ef8a

Tx prefix hash: 55a3ecdcde84b434d59630faa259b261b592cfefaa85c8325ac7caf80323c9c9
Tx public key: c2cdb8d88fcaeb10f910b056a138318acd2c37a8c23964bd4d3fe2aad07ab76f
Timestamp: 1572870415 Timestamp [UTC]: 2019-11-04 12:26:55 Age [y:d:h:m:s]: 06:108:21:45:15
Block: 608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0801 kB
Tx version: 2 No of confirmations: 1480523 RingCT/type: yes/0
Extra: 01c2cdb8d88fcaeb10f910b056a138318acd2c37a8c23964bd4d3fe2aad07ab76f

1 output(s) for total of 0.610922821505 xmr

stealth address amount amount idx tag
00: 417cb4874a5f875e1bc3937df461b52f70c5ea1160d65f49e363fc6529e5bd2c 0.610922821505 562 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 dinastycoin-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": 618, "vin": [ { "gen": { "height": 608 } } ], "vout": [ { "amount": 610922821505, "target": { "key": "417cb4874a5f875e1bc3937df461b52f70c5ea1160d65f49e363fc6529e5bd2c" } } ], "extra": [ 1, 194, 205, 184, 216, 143, 202, 235, 16, 249, 16, 176, 86, 161, 56, 49, 138, 205, 44, 55, 168, 194, 57, 100, 189, 77, 63, 226, 170, 208, 122, 183, 111 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369