Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 746f929d1f8dbba9a993f8eb84b3eb6821e59b45b9966a49a641dcc5455f2c69

Tx prefix hash: 366440e47084c77fb4aa9d9941998bea877579d050275881d265a3330ee5af1a
Tx public key: 364898794cc0bc895563b4a5d4501eb1fb5ce7e163245d6a576c699c0c26e98b
Timestamp: 1577216083 Timestamp [UCT]: 2019-12-24 19:34:43 Age [y:d:h:m:s]: 05:047:11:14:22
Block: 30992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1183627 RingCT/type: yes/0
Extra: 01364898794cc0bc895563b4a5d4501eb1fb5ce7e163245d6a576c699c0c26e98b0211000000144ac5aa02000000000000000000

1 output(s) for total of 484.555496708000 dcy

stealth address amount amount idx
00: 7c06f2b39efcf9c6c48a3602f7f0c6c2550c25ff062089cbcd32d197a63b8d71 484.555496708000 51176 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": 31002, "vin": [ { "gen": { "height": 30992 } } ], "vout": [ { "amount": 484555496708, "target": { "key": "7c06f2b39efcf9c6c48a3602f7f0c6c2550c25ff062089cbcd32d197a63b8d71" } } ], "extra": [ 1, 54, 72, 152, 121, 76, 192, 188, 137, 85, 99, 180, 165, 212, 80, 30, 177, 251, 92, 231, 225, 99, 36, 93, 106, 87, 108, 105, 156, 12, 38, 233, 139, 2, 17, 0, 0, 0, 20, 74, 197, 170, 2, 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