Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aada96e14d1d8fbfd8f66d07361339d6196d35bceaacb36649bd7fba82e90e2

Tx prefix hash: 030191ada042a3fe656d1cec096c5c3397b05efb47c3ac48f119f3150a30caec
Tx public key: 552087e5e0a989d24222df1544500e26114044fa3b35444a3392d93fb64ca3d3
Timestamp: 1583858958 Timestamp [UCT]: 2020-03-10 16:49:18 Age [y:d:h:m:s]: 04:290:13:29:36
Block: 80067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102625 RingCT/type: yes/0
Extra: 01552087e5e0a989d24222df1544500e26114044fa3b35444a3392d93fb64ca3d302110000000178e4872e000000000000000000

1 output(s) for total of 333.200451680000 dcy

stealth address amount amount idx
00: 28f7b1ac2a72ed7f2f54a8ebf1766bfe8f15f07e8a81535ca633d7a9d9a18032 333.200451680000 146487 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": 80077, "vin": [ { "gen": { "height": 80067 } } ], "vout": [ { "amount": 333200451680, "target": { "key": "28f7b1ac2a72ed7f2f54a8ebf1766bfe8f15f07e8a81535ca633d7a9d9a18032" } } ], "extra": [ 1, 85, 32, 135, 229, 224, 169, 137, 210, 66, 34, 223, 21, 68, 80, 14, 38, 17, 64, 68, 250, 59, 53, 68, 74, 51, 146, 217, 63, 182, 76, 163, 211, 2, 17, 0, 0, 0, 1, 120, 228, 135, 46, 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