Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b480ed08ea5d31ac30c396590add1d2d9bb665e962eb365e17d143c48153e53

Tx prefix hash: 4bb80e07eb6bf97a9ae3484c4e53050a529f82b5b12299e1228c56efd8bea826
Tx public key: 9ab9a3a260eb422c92c42e6d56e45b8616eaabfd171584b7d2fb7ee0bc66af86
Timestamp: 1736683235 Timestamp [UCT]: 2025-01-12 12:00:35 Age [y:d:h:m:s]: 00:157:00:31:19
Block: 1195725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111932 RingCT/type: yes/0
Extra: 019ab9a3a260eb422c92c42e6d56e45b8616eaabfd171584b7d2fb7ee0bc66af860211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cea84b46cc40e593f4b085222b5fe6958080f94a913fc25b99a317a0dd8035ac 0.600000000000 1682318 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": 1195735, "vin": [ { "gen": { "height": 1195725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cea84b46cc40e593f4b085222b5fe6958080f94a913fc25b99a317a0dd8035ac" } } ], "extra": [ 1, 154, 185, 163, 162, 96, 235, 66, 44, 146, 196, 46, 109, 86, 228, 91, 134, 22, 234, 171, 253, 23, 21, 132, 183, 210, 251, 126, 224, 188, 102, 175, 134, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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