Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb633f06fb11d35ad5ac6ff5a0e85ce3f7d994befae6c2814d2f378e3fd6d9e4

Tx prefix hash: 156c2b0bd64122e4a38fdcfd9fa051d8cf2ab100d1e7aabf3890bd3c34852cc0
Tx public key: 6d17841b3e65d0288b6149f7d69c1aed244db4a85b9929128c2b2b2c81a8f6d2
Timestamp: 1714004815 Timestamp [UCT]: 2024-04-25 00:26:55 Age [y:d:h:m:s]: 00:346:12:31:16
Block: 1007850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247710 RingCT/type: yes/0
Extra: 016d17841b3e65d0288b6149f7d69c1aed244db4a85b9929128c2b2b2c81a8f6d20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26975604cffb9da95725ac9317e244f11931c463412e8434a7a7a01079e6eb8e 0.600000000000 1469316 of 15

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": 1007860, "vin": [ { "gen": { "height": 1007850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26975604cffb9da95725ac9317e244f11931c463412e8434a7a7a01079e6eb8e" } } ], "extra": [ 1, 109, 23, 132, 27, 62, 101, 208, 40, 139, 97, 73, 247, 214, 156, 26, 237, 36, 77, 180, 168, 91, 153, 41, 18, 140, 43, 43, 44, 129, 168, 246, 210, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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