Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63561470d3fa9ede9c48651e98538a4f061dd863a80bf2553f7aaf5cad99d95

Tx prefix hash: 3eaebe909779f84f7a5f8e391c6cd557b59ef1688c73de53087614075659c170
Tx public key: f1d825f3d6925b525b5760f7426f3633f705d80d0f17394309f0fb34904b37d8
Timestamp: 1579869196 Timestamp [UTC]: 2020-01-24 12:33:16 Age [y:d:h:m:s]: 06:012:00:28:31
Block: 51796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1417986 RingCT/type: yes/0
Extra: 01f1d825f3d6925b525b5760f7426f3633f705d80d0f17394309f0fb34904b37d80211000000084ac5aa02000000000000000000

1 output(s) for total of 0.413408289622 xmr

stealth address amount amount idx tag
00: 17540fcbccce541ff2bb05ac00ec75cbcb561a486cea5b868f078375521bfb5c 0.413408289622 96080 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": 51806, "vin": [ { "gen": { "height": 51796 } } ], "vout": [ { "amount": 413408289622, "target": { "key": "17540fcbccce541ff2bb05ac00ec75cbcb561a486cea5b868f078375521bfb5c" } } ], "extra": [ 1, 241, 216, 37, 243, 214, 146, 91, 82, 91, 87, 96, 247, 66, 111, 54, 51, 247, 5, 216, 13, 15, 23, 57, 67, 9, 240, 251, 52, 144, 75, 55, 216, 2, 17, 0, 0, 0, 8, 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