Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04627983a5912dfd92cf6c19e75892ef009181a44a6d1e6ee9bedcd780151e59

Tx prefix hash: 9d12fddffb07bb8f21e38ab39c84af2caf1b82fb753d932f072cab16e9111057
Tx public key: 2cf005372bf5518d3b4c4df86c117269a21682465bdae28c973fce200c24b0fc
Timestamp: 1725231483 Timestamp [UCT]: 2024-09-01 22:58:03 Age [y:d:h:m:s]: 00:211:02:06:29
Block: 1100929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150706 RingCT/type: yes/0
Extra: 012cf005372bf5518d3b4c4df86c117269a21682465bdae28c973fce200c24b0fc02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe8318e2f35295a7f67ba4f4599e0cd254a9f8eae710ce2d2bfa699dd718c64d 0.600000000000 1576910 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": 1100939, "vin": [ { "gen": { "height": 1100929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe8318e2f35295a7f67ba4f4599e0cd254a9f8eae710ce2d2bfa699dd718c64d" } } ], "extra": [ 1, 44, 240, 5, 55, 43, 245, 81, 141, 59, 76, 77, 248, 108, 17, 114, 105, 162, 22, 130, 70, 91, 218, 226, 140, 151, 63, 206, 32, 12, 36, 176, 252, 2, 17, 0, 0, 0, 1, 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