Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2359804b6a13628d051246f1c12a93269b7f4cd816a1bd8ea78987ce099c7bc

Tx prefix hash: 102d9eecd0d256bd47e403d1f0003523333bcee697ad03b9e2553f8f8c5ac0ee
Tx public key: 2c8b973ec9f7cf64db47c1f3f139338aa4148e124a90f278b763e8fb4c4850aa
Timestamp: 1733787275 Timestamp [UCT]: 2024-12-09 23:34:35 Age [y:d:h:m:s]: 00:103:08:52:41
Block: 1171764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73663 RingCT/type: yes/0
Extra: 012c8b973ec9f7cf64db47c1f3f139338aa4148e124a90f278b763e8fb4c4850aa021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb9f6a726d3902674c70e5d80c434c4b00e6dcaa87f27570e2ec42d8b2bfe17d 0.600000000000 1657563 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": 1171774, "vin": [ { "gen": { "height": 1171764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb9f6a726d3902674c70e5d80c434c4b00e6dcaa87f27570e2ec42d8b2bfe17d" } } ], "extra": [ 1, 44, 139, 151, 62, 201, 247, 207, 100, 219, 71, 193, 243, 241, 57, 51, 138, 164, 20, 142, 18, 74, 144, 242, 120, 183, 99, 232, 251, 76, 72, 80, 170, 2, 17, 0, 0, 0, 5, 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