Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e98147934f19257fbc8cc481cff7dbb70d227c35938f20baf764b5fc0379523

Tx prefix hash: 33cad0edb4f2e25da3d7dc9c121c706f39ce3fd930705b9233021e4ebd3b65cf
Tx public key: 520aa1cc915c27f3856a386f02fd13e9f2e2ff1ff877cc0fb2684c9d02b1613c
Timestamp: 1737602970 Timestamp [UCT]: 2025-01-23 03:29:30 Age [y:d:h:m:s]: 00:145:01:03:51
Block: 1203297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103410 RingCT/type: yes/0
Extra: 01520aa1cc915c27f3856a386f02fd13e9f2e2ff1ff877cc0fb2684c9d02b1613c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72096cfd2273b8a71d30bbebabb11b0867b4f319d910d76b50eb6240022fc7ad 0.600000000000 1689972 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": 1203307, "vin": [ { "gen": { "height": 1203297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72096cfd2273b8a71d30bbebabb11b0867b4f319d910d76b50eb6240022fc7ad" } } ], "extra": [ 1, 82, 10, 161, 204, 145, 92, 39, 243, 133, 106, 56, 111, 2, 253, 19, 233, 242, 226, 255, 31, 248, 119, 204, 15, 178, 104, 76, 157, 2, 177, 97, 60, 2, 17, 0, 0, 0, 3, 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