Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efe045611042bfdf0734da41ea3d5db4077aab7fe8f88c0629a7270b1c677df8

Tx prefix hash: 607dc2b82360142374d7ec367a76b2e895c7f01c1c215b7f03b5294c4cd60fad
Tx public key: fef6ba45830344f36f2fe36d12a5e8f1ed991399550c748bf9b452a447ede170
Timestamp: 1710858902 Timestamp [UCT]: 2024-03-19 14:35:02 Age [y:d:h:m:s]: 01:058:20:09:29
Block: 981787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303048 RingCT/type: yes/0
Extra: 01fef6ba45830344f36f2fe36d12a5e8f1ed991399550c748bf9b452a447ede17002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30729dc8cff8c082ba08f12ca7cacde45847337e81b0a64f44c52741d2e1a9eb 0.600000000000 1441886 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": 981797, "vin": [ { "gen": { "height": 981787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30729dc8cff8c082ba08f12ca7cacde45847337e81b0a64f44c52741d2e1a9eb" } } ], "extra": [ 1, 254, 246, 186, 69, 131, 3, 68, 243, 111, 47, 227, 109, 18, 165, 232, 241, 237, 153, 19, 153, 85, 12, 116, 139, 249, 180, 82, 164, 71, 237, 225, 112, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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