Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4c7b1364fe566fd0293f210d2d47de5d33f0b35e3eb5a2d936b05adaccb679

Tx prefix hash: 7428defad8dad4d00c738e9c4574d17ee37a32a707db75e683cc2dfbb284cf9d
Tx public key: 1e34e63396f2c9a943371b5250855759c548639307a26f738934db1e3cf754eb
Timestamp: 1651088160 Timestamp [UTC]: 2022-04-27 19:36:00 Age [y:d:h:m:s]: 03:296:18:43:53
Block: 489426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 990391 RingCT/type: yes/0
Extra: 011e34e63396f2c9a943371b5250855759c548639307a26f738934db1e3cf754eb021100000001c9067537000000000000000000

1 output(s) for total of 0.014666575175 xmr

stealth address amount amount idx tag
00: 4b701e3f36e43f602b0055fd453ed62790dd9f6bbf543416fe80ba5eb2da9348 0.014666575175 912233 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": 489436, "vin": [ { "gen": { "height": 489426 } } ], "vout": [ { "amount": 14666575175, "target": { "key": "4b701e3f36e43f602b0055fd453ed62790dd9f6bbf543416fe80ba5eb2da9348" } } ], "extra": [ 1, 30, 52, 230, 51, 150, 242, 201, 169, 67, 55, 27, 82, 80, 133, 87, 89, 197, 72, 99, 147, 7, 162, 111, 115, 137, 52, 219, 30, 60, 247, 84, 235, 2, 17, 0, 0, 0, 1, 201, 6, 117, 55, 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