Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00d522a54399318ad0b26acb9b51f4ef27d63c27093dde57c3af9fc133de32d2

Tx prefix hash: a636760740487a7fef196038e61f7850b25df0a0d27bce4199d89ea85d6d30f2
Tx public key: 895a624223fe924c8d927265c0eb4c08a3f3c8d1db99c799b55e32c01f7e70dd
Timestamp: 1710046701 Timestamp [UCT]: 2024-03-10 04:58:21 Age [y:d:h:m:s]: 00:350:12:03:16
Block: 975045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250586 RingCT/type: yes/0
Extra: 01895a624223fe924c8d927265c0eb4c08a3f3c8d1db99c799b55e32c01f7e70dd0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff1e70acf3fa7ee31d6e5580f85995a665d464b0fd10350e5e0ee8d25e1122cb 0.600000000000 1435016 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": 975055, "vin": [ { "gen": { "height": 975045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff1e70acf3fa7ee31d6e5580f85995a665d464b0fd10350e5e0ee8d25e1122cb" } } ], "extra": [ 1, 137, 90, 98, 66, 35, 254, 146, 76, 141, 146, 114, 101, 192, 235, 76, 8, 163, 243, 200, 209, 219, 153, 199, 153, 181, 94, 50, 192, 31, 126, 112, 221, 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