Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f295dfee98e7be0bbd23204b5543f1e66533f7a1ed8a9adab9d410a67bf41d

Tx prefix hash: 3b38aed90bdb248061eedbd0afa75b003e4ca3cf6732e17d9eb7c9731daa8c17
Tx public key: 79791886670d6db2602a0cdb7514cf1ddbf2e86bd10f975d3a97487fd260d836
Timestamp: 1683607962 Timestamp [UCT]: 2023-05-09 04:52:42 Age [y:d:h:m:s]: 01:256:23:04:55
Block: 756101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445065 RingCT/type: yes/0
Extra: 0179791886670d6db2602a0cdb7514cf1ddbf2e86bd10f975d3a97487fd260d836021100000009b3164c24000000000000000000

1 output(s) for total of 1.917448502000 dcy

stealth address amount amount idx
00: 989825eae6e6bb7fbfa24e1a4fb70e5b2e081538bfe1ce7dbd55299cceea15ff 1.917448502000 1204448 of 0

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": 756111, "vin": [ { "gen": { "height": 756101 } } ], "vout": [ { "amount": 1917448502, "target": { "key": "989825eae6e6bb7fbfa24e1a4fb70e5b2e081538bfe1ce7dbd55299cceea15ff" } } ], "extra": [ 1, 121, 121, 24, 134, 103, 13, 109, 178, 96, 42, 12, 219, 117, 20, 207, 29, 219, 242, 232, 107, 209, 15, 151, 93, 58, 151, 72, 127, 210, 96, 216, 54, 2, 17, 0, 0, 0, 9, 179, 22, 76, 36, 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