Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d2de3f92204ef42c756e4b5302b9e57a399ae4f4e151daf48eea490b2b3c09b

Tx prefix hash: 6b7015af79999821b621a3d30a1f803ad5da1b67f5071982b14bc6d8c34c3abe
Tx public key: d8130c7732d6cba72604e0be583984fbcb5a7c11f003a55f0e187582f13e11c6
Timestamp: 1576369876 Timestamp [UTC]: 2019-12-15 00:31:16 Age [y:d:h:m:s]: 06:068:03:09:25
Block: 27131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1453807 RingCT/type: yes/0
Extra: 01d8130c7732d6cba72604e0be583984fbcb5a7c11f003a55f0e187582f13e11c602110000001e4ac5aa02000000000000000000

1 output(s) for total of 0.499013269465 xmr

stealth address amount amount idx tag
00: fea2c89b8747f9810360ce4112fc4e5d90c50d8b4f119f3e4652d9b1093e69d7 0.499013269465 44972 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": 27141, "vin": [ { "gen": { "height": 27131 } } ], "vout": [ { "amount": 499013269465, "target": { "key": "fea2c89b8747f9810360ce4112fc4e5d90c50d8b4f119f3e4652d9b1093e69d7" } } ], "extra": [ 1, 216, 19, 12, 119, 50, 214, 203, 167, 38, 4, 224, 190, 88, 57, 132, 251, 203, 90, 124, 17, 240, 3, 165, 95, 14, 24, 117, 130, 241, 62, 17, 198, 2, 17, 0, 0, 0, 30, 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