Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 248ec0a742ad0d55f4dd0423b8003ea5677fcefb34f5aaed22fadc4899151d25

Tx prefix hash: 6e944b1c9c8a066ff75cae1d1bd85bef80889f5bc0ca8592afa8ca2b73e3bbca
Tx public key: 6c750fe6462fd160e535a3f419bd4c54c4de7c4469957f03fa42d2d3044af736
Timestamp: 1712235879 Timestamp [UCT]: 2024-04-04 13:04:39 Age [y:d:h:m:s]: 01:011:03:55:11
Block: 993157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268971 RingCT/type: yes/0
Extra: 016c750fe6462fd160e535a3f419bd4c54c4de7c4469957f03fa42d2d3044af7360211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 533944b54960a2d691b4fe6dcf338e5f650bde8c573c05f91cebafafe06fefad 0.600000000000 1453539 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": 993167, "vin": [ { "gen": { "height": 993157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "533944b54960a2d691b4fe6dcf338e5f650bde8c573c05f91cebafafe06fefad" } } ], "extra": [ 1, 108, 117, 15, 230, 70, 47, 209, 96, 229, 53, 163, 244, 25, 189, 76, 84, 196, 222, 124, 68, 105, 149, 127, 3, 250, 66, 210, 211, 4, 74, 247, 54, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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