Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17e98d8a6179eb039202147020cb57924e69309d4a6169d357524a6370aca2b7

Tx prefix hash: c5a22371d642e76349b0e8ee9c8e5305e766051231f6efa513fd0a1f028c5c52
Tx public key: 8cdbe20b27b550b9bcda77be8f06f44cebe0e1ca6e89c3f7f53bf0abe5604b47
Timestamp: 1737380353 Timestamp [UCT]: 2025-01-20 13:39:13 Age [y:d:h:m:s]: 00:149:04:55:43
Block: 1201447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106380 RingCT/type: yes/0
Extra: 018cdbe20b27b550b9bcda77be8f06f44cebe0e1ca6e89c3f7f53bf0abe5604b47021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 363667b351e0e71d0a0fda6d66e0e5b862e5eaddb292be33048e27bc915c13ff 0.600000000000 1688100 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": 1201457, "vin": [ { "gen": { "height": 1201447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "363667b351e0e71d0a0fda6d66e0e5b862e5eaddb292be33048e27bc915c13ff" } } ], "extra": [ 1, 140, 219, 226, 11, 39, 181, 80, 185, 188, 218, 119, 190, 143, 6, 244, 76, 235, 224, 225, 202, 110, 137, 195, 247, 245, 59, 240, 171, 229, 96, 75, 71, 2, 17, 0, 0, 0, 4, 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