Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86141456bdb7670bcad6e707ea6cde0202adff0a11a5497d912c87e44ff47a6d

Tx prefix hash: f834a0cba97ee48fb5e1c252338fb6cb41bf40e8b329b53ac115d9e98209af96
Tx public key: c7d6a38ed1f62798eae9546bf82edc45303df36a592e35d731d0e1ed8f3fbfe3
Timestamp: 1734401028 Timestamp [UCT]: 2024-12-17 02:03:48 Age [y:d:h:m:s]: 00:141:10:01:02
Block: 1176853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100859 RingCT/type: yes/0
Extra: 01c7d6a38ed1f62798eae9546bf82edc45303df36a592e35d731d0e1ed8f3fbfe3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 032e699ebfceba20ce57b5f9c1f2d6ecb29c6832ac6a4a703f06bdd334a2d8f6 0.600000000000 1663214 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": 1176863, "vin": [ { "gen": { "height": 1176853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "032e699ebfceba20ce57b5f9c1f2d6ecb29c6832ac6a4a703f06bdd334a2d8f6" } } ], "extra": [ 1, 199, 214, 163, 142, 209, 246, 39, 152, 234, 233, 84, 107, 248, 46, 220, 69, 48, 61, 243, 106, 89, 46, 53, 215, 49, 208, 225, 237, 143, 63, 191, 227, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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