Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d270599672de49aca49a36fdae0247f87eaa9ac5eb4d7d221b2283fb5a73760

Tx prefix hash: b1d0b272f45f51462a10be691e01f75071bacf4cbb25abf2c6820ecd2927e87d
Tx public key: 740fc4bbeb022dc0c81753eebf18361a741801d0750e9061a67d064697b21bfe
Timestamp: 1739110568 Timestamp [UCT]: 2025-02-09 14:16:08 Age [y:d:h:m:s]: 00:031:03:18:23
Block: 1215559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22279 RingCT/type: yes/0
Extra: 01740fc4bbeb022dc0c81753eebf18361a741801d0750e9061a67d064697b21bfe0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 207c3bafb2612f515e3e92bda7af9b56a05c3a9e3b36b7433b4f414f27d9d19d 0.600000000000 1702358 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": 1215569, "vin": [ { "gen": { "height": 1215559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "207c3bafb2612f515e3e92bda7af9b56a05c3a9e3b36b7433b4f414f27d9d19d" } } ], "extra": [ 1, 116, 15, 196, 187, 235, 2, 45, 192, 200, 23, 83, 238, 191, 24, 54, 26, 116, 24, 1, 208, 117, 14, 144, 97, 166, 125, 6, 70, 151, 178, 27, 254, 2, 17, 0, 0, 0, 5, 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