Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765478b53a8d8d4ecdadc1efdbe09ebc033d91cac032b4197153b9fb8a75afd6

Tx prefix hash: 631dd2136825bb48a56ba41398b4bde800541642d9db0c35074084cb618a7430
Tx public key: ebd5e7cc515ae4870b00f6244062ecf0aebfcb88c799c327e07626a335e3d394
Timestamp: 1737045492 Timestamp [UCT]: 2025-01-16 16:38:12 Age [y:d:h:m:s]: 00:151:19:51:35
Block: 1198722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108233 RingCT/type: yes/0
Extra: 01ebd5e7cc515ae4870b00f6244062ecf0aebfcb88c799c327e07626a335e3d394021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 454006bb8c8ee7ced6d561a63899e9d51e7b0f4a383b048ec40c9989e6bd8a06 0.600000000000 1685349 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": 1198732, "vin": [ { "gen": { "height": 1198722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "454006bb8c8ee7ced6d561a63899e9d51e7b0f4a383b048ec40c9989e6bd8a06" } } ], "extra": [ 1, 235, 213, 231, 204, 81, 90, 228, 135, 11, 0, 246, 36, 64, 98, 236, 240, 174, 191, 203, 136, 199, 153, 195, 39, 224, 118, 38, 163, 53, 227, 211, 148, 2, 17, 0, 0, 0, 1, 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