Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b6af9fd22fbd95869447773829ba53209c0962de462a281754b8bc3fac738fb

Tx prefix hash: 0971d09021aa0f68f15af178ee422ea2abd28090426cdeec4d5a3dab0a670197
Tx public key: f00a3d767fb338125d37e771ba61d564da3b1b9e0574dc6dd8318c05ab8ce6c6
Timestamp: 1668634191 Timestamp [UCT]: 2022-11-16 21:29:51 Age [y:d:h:m:s]: 02:060:01:55:53
Block: 632635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564857 RingCT/type: yes/0
Extra: 01f00a3d767fb338125d37e771ba61d564da3b1b9e0574dc6dd8318c05ab8ce6c602110000000333af99f4000000000000000000

1 output(s) for total of 4.918329693000 dcy

stealth address amount amount idx
00: 3e7c2fc08be6f7d385b289a469353329e6e505aefd6c6e76d9a943e7cca2f32d 4.918329693000 1071621 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": 632645, "vin": [ { "gen": { "height": 632635 } } ], "vout": [ { "amount": 4918329693, "target": { "key": "3e7c2fc08be6f7d385b289a469353329e6e505aefd6c6e76d9a943e7cca2f32d" } } ], "extra": [ 1, 240, 10, 61, 118, 127, 179, 56, 18, 93, 55, 231, 113, 186, 97, 213, 100, 218, 59, 27, 158, 5, 116, 220, 109, 216, 49, 140, 5, 171, 140, 230, 198, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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