Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e127750d0294331e36b6f7600a19fd4254608e05fbdeb764691820844a0f516

Tx prefix hash: b8bcb1710195009316ae7eae8b14df6e46f3d1b68f98efb2bf1180ff650b8f5b
Tx public key: 589a75b36793df839862b3e9631f1fa083fba751352f1ff9220d4a65d7a04529
Timestamp: 1577829441 Timestamp [UCT]: 2019-12-31 21:57:21 Age [y:d:h:m:s]: 04:363:11:15:33
Block: 36027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148882 RingCT/type: yes/0
Extra: 01589a75b36793df839862b3e9631f1fa083fba751352f1ff9220d4a65d7a0452902110000004a78873133000000000000000000

1 output(s) for total of 466.260308759000 dcy

stealth address amount amount idx
00: db1a2cae3ddac632e9e80964c13c4dc2c8ae03fcc1f3f502fd7e7bb83ef5a7e7 466.260308759000 60875 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": 36037, "vin": [ { "gen": { "height": 36027 } } ], "vout": [ { "amount": 466260308759, "target": { "key": "db1a2cae3ddac632e9e80964c13c4dc2c8ae03fcc1f3f502fd7e7bb83ef5a7e7" } } ], "extra": [ 1, 88, 154, 117, 179, 103, 147, 223, 131, 152, 98, 179, 233, 99, 31, 31, 160, 131, 251, 167, 81, 53, 47, 31, 249, 34, 13, 74, 101, 215, 160, 69, 41, 2, 17, 0, 0, 0, 74, 120, 135, 49, 51, 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