Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1925f4738091323f067dbe2797044d2e8703924604d199528d6e2eaf8826c93

Tx prefix hash: 11c2405c2aadd95fedabbbec5e1979eb01e4d2299f38439be67c9be8f5462128
Tx public key: 9b18c8f17b4a2a0be9e9b7340c41b0c414ab9140d3bbaa24d19f03f0eccc865e
Timestamp: 1718684773 Timestamp [UCT]: 2024-06-18 04:26:13 Age [y:d:h:m:s]: 01:142:15:52:42
Block: 1046653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360513 RingCT/type: yes/0
Extra: 019b18c8f17b4a2a0be9e9b7340c41b0c414ab9140d3bbaa24d19f03f0eccc865e0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24293b1dacd44528a4e1ed61749744b9b4ce65b929d7c1254f7bff25140e87bb 0.600000000000 1516470 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": 1046663, "vin": [ { "gen": { "height": 1046653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24293b1dacd44528a4e1ed61749744b9b4ce65b929d7c1254f7bff25140e87bb" } } ], "extra": [ 1, 155, 24, 200, 241, 123, 74, 42, 11, 233, 233, 183, 52, 12, 65, 176, 196, 20, 171, 145, 64, 211, 187, 170, 36, 209, 159, 3, 240, 236, 204, 134, 94, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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