Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63c5fd0e044007ebf5371f6c2fb00b1d6dcbeaf6d5b8715f85bf9639076e6e9e

Tx prefix hash: bd5d86f5b379cab0b0f1d7acaf80b90e1e8ae97806f2c54d877909358a998a47
Tx public key: 47b71e5913d6a9952b1beac37abde7e7aebc407d02b286a4247eb59ea9b02bc0
Timestamp: 1731433457 Timestamp [UCT]: 2024-11-12 17:44:17 Age [y:d:h:m:s]: 01:078:00:48:38
Block: 1152257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314105 RingCT/type: yes/0
Extra: 0147b71e5913d6a9952b1beac37abde7e7aebc407d02b286a4247eb59ea9b02bc0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28b89bd7768666c70dd40b04c15c0f5d485cb919818108d72d37e0bf3f07c3b5 0.600000000000 1637850 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": 1152267, "vin": [ { "gen": { "height": 1152257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b89bd7768666c70dd40b04c15c0f5d485cb919818108d72d37e0bf3f07c3b5" } } ], "extra": [ 1, 71, 183, 30, 89, 19, 214, 169, 149, 43, 27, 234, 195, 122, 189, 231, 231, 174, 188, 64, 125, 2, 178, 134, 164, 36, 126, 181, 158, 169, 176, 43, 192, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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