Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f5ebe91ca275219a837ba19df56e5067d4723f1d867567006b2a4b5bd76d637

Tx prefix hash: c2d761bc8df1ab83f9bdeb669c1a32247ae0e3229dda54e1b998d662f18b156c
Tx public key: eb2ba09a9f95760cc736c234310b52d30106f60bcb1d99ca32ca8bd4a8af33ce
Timestamp: 1582433810 Timestamp [UCT]: 2020-02-23 04:56:50 Age [y:d:h:m:s]: 04:307:00:22:19
Block: 70576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112081 RingCT/type: yes/0
Extra: 01eb2ba09a9f95760cc736c234310b52d30106f60bcb1d99ca32ca8bd4a8af33ce02110000000103d36d11000000000000000000

1 output(s) for total of 358.222794371000 dcy

stealth address amount amount idx
00: 4bf964d70fcb1eb14b2a0f62af5e25201229b62d044afa933a80cf9bf9d0d7fc 358.222794371000 130424 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 dinasty-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": 70586, "vin": [ { "gen": { "height": 70576 } } ], "vout": [ { "amount": 358222794371, "target": { "key": "4bf964d70fcb1eb14b2a0f62af5e25201229b62d044afa933a80cf9bf9d0d7fc" } } ], "extra": [ 1, 235, 43, 160, 154, 159, 149, 118, 12, 199, 54, 194, 52, 49, 11, 82, 211, 1, 6, 246, 11, 203, 29, 153, 202, 50, 202, 139, 212, 168, 175, 51, 206, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8