Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63cb5a83085ee73d146e8445cf7a4efe5a523dd41a37a6f0bb75b34cb4f67f60

Tx prefix hash: 6f2de89b808525fd3edd8f57dd049891e3ca7bbc39345c4815e28f6f00714be2
Tx public key: 64ae2f1d34c3dfabf6ab6d024252c6fb0c6d81f3924a35451c0190406ac2f153
Timestamp: 1576422773 Timestamp [UTC]: 2019-12-15 15:12:53 Age [y:d:h:m:s]: 06:065:22:39:53
Block: 27243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1452559 RingCT/type: yes/0
Extra: 0164ae2f1d34c3dfabf6ab6d024252c6fb0c6d81f3924a35451c0190406ac2f1530211000000014ac5aa02000000000000000000

1 output(s) for total of 0.498578444380 xmr

stealth address amount amount idx tag
00: b385491b9eaeb14c6b4976a5fbc50b09a7861ebf19acd2334f4569277757f225 0.498578444380 45216 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": 27253, "vin": [ { "gen": { "height": 27243 } } ], "vout": [ { "amount": 498578444380, "target": { "key": "b385491b9eaeb14c6b4976a5fbc50b09a7861ebf19acd2334f4569277757f225" } } ], "extra": [ 1, 100, 174, 47, 29, 52, 195, 223, 171, 246, 171, 109, 2, 66, 82, 198, 251, 12, 109, 129, 243, 146, 74, 53, 69, 28, 1, 144, 64, 106, 194, 241, 83, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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