Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f369609f86a932598de13eae161f947114f6bbd7d00d11fcf1ab0e33f3e007d4

Tx prefix hash: 65e416b4b192b49b51d76e0983383bc43d8a7be7cc0242c364d95f75d4297fc6
Tx public key: ebc2707c35f5323d189a80ff421d98a716b5a909286a120cb608439e346614e3
Timestamp: 1725684085 Timestamp [UCT]: 2024-09-07 04:41:25 Age [y:d:h:m:s]: 00:231:04:56:02
Block: 1104678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165099 RingCT/type: yes/0
Extra: 01ebc2707c35f5323d189a80ff421d98a716b5a909286a120cb608439e346614e302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 385e29cd1b430aad95d50dbc872a9f7286522b8a9a50190c4b50d2d8717f8c52 0.600000000000 1581911 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": 1104688, "vin": [ { "gen": { "height": 1104678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "385e29cd1b430aad95d50dbc872a9f7286522b8a9a50190c4b50d2d8717f8c52" } } ], "extra": [ 1, 235, 194, 112, 124, 53, 245, 50, 61, 24, 154, 128, 255, 66, 29, 152, 167, 22, 181, 169, 9, 40, 106, 18, 12, 182, 8, 67, 158, 52, 102, 20, 227, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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