Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bbf350e26519a70ed30cb73fb00aaa0081f37f33efce85c159f42979e9b768d

Tx prefix hash: ce8ed08eafc8fe292ab8786ec07f4e12921df85fb58300ba2df1e14ad923d171
Tx public key: 65b5e84e24eb83f8e9c42f5b5956fd9559734d7c3db551f207b5a1e2ad60c522
Timestamp: 1715367452 Timestamp [UCT]: 2024-05-10 18:57:32 Age [y:d:h:m:s]: 00:244:13:30:55
Block: 1019164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175022 RingCT/type: yes/0
Extra: 0165b5e84e24eb83f8e9c42f5b5956fd9559734d7c3db551f207b5a1e2ad60c522021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9297abae77fb395b9c6d423d70d3deaa3b181d89f3bb034e60d98560859ddc6 0.600000000000 1483061 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": 1019174, "vin": [ { "gen": { "height": 1019164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9297abae77fb395b9c6d423d70d3deaa3b181d89f3bb034e60d98560859ddc6" } } ], "extra": [ 1, 101, 181, 232, 78, 36, 235, 131, 248, 233, 196, 47, 91, 89, 86, 253, 149, 89, 115, 77, 124, 61, 181, 81, 242, 7, 181, 161, 226, 173, 96, 197, 34, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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