Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f072a790743ef8d21ed8070c7bd4cb6bc9682e9cc1907600aa15ce82a5d2cd3

Tx prefix hash: f224bd5be56ac09df327f09576ffb5e1cbc03a5df0a3268b9bcb7e964eb0c584
Tx public key: 30de9db1fc89a066ec1fd6b275414764f1ed0a76e8605da726482d87aaddd042
Timestamp: 1733575776 Timestamp [UCT]: 2024-12-07 12:49:36 Age [y:d:h:m:s]: 00:113:13:39:14
Block: 1170000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80962 RingCT/type: yes/0
Extra: 0130de9db1fc89a066ec1fd6b275414764f1ed0a76e8605da726482d87aaddd042021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdd4964f22e3c2c067d62a15b19013a402021b9b3e59692415b0e438742fcfe6 0.600000000000 1655727 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": 1170010, "vin": [ { "gen": { "height": 1170000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdd4964f22e3c2c067d62a15b19013a402021b9b3e59692415b0e438742fcfe6" } } ], "extra": [ 1, 48, 222, 157, 177, 252, 137, 160, 102, 236, 31, 214, 178, 117, 65, 71, 100, 241, 237, 10, 118, 232, 96, 93, 167, 38, 72, 45, 135, 170, 221, 208, 66, 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