Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4589fbff9c71d02526e53add7d465cdce72f95c8325a6c078d68f496eb8df885

Tx prefix hash: 94a0c4cf33da5abea64e5cb4ea35f1191f20f39be9e02bf67b678db863b7f267
Tx public key: b5dca8c297e2ce243702f0b6f786a047098308b62f68625ea19739443769bf28
Timestamp: 1577946337 Timestamp [UCT]: 2020-01-02 06:25:37 Age [y:d:h:m:s]: 05:063:09:42:52
Block: 36974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195092 RingCT/type: yes/0
Extra: 01b5dca8c297e2ce243702f0b6f786a047098308b62f68625ea19739443769bf280211000000134943cd9f000000000000000000

1 output(s) for total of 462.903688603000 dcy

stealth address amount amount idx
00: 117075c3c1ef70f5257aab98e8fcfd39a5d1152e9ae1f43af989e0bb3f101728 462.903688603000 62698 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": 36984, "vin": [ { "gen": { "height": 36974 } } ], "vout": [ { "amount": 462903688603, "target": { "key": "117075c3c1ef70f5257aab98e8fcfd39a5d1152e9ae1f43af989e0bb3f101728" } } ], "extra": [ 1, 181, 220, 168, 194, 151, 226, 206, 36, 55, 2, 240, 182, 247, 134, 160, 71, 9, 131, 8, 182, 47, 104, 98, 94, 161, 151, 57, 68, 55, 105, 191, 40, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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