Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53b867ff72340edeba98bb57c2cea7ff6bd622b6c0d09d54e3e08275b81e9267

Tx prefix hash: 43443d9f8b143f716ad410edae36e0b63a6ac659c3ac0f4c3f74808478c807af
Tx public key: 59352363a01bf89d2b4113927b43622d5b97b489a42170f0648c9b8045a3c8db
Timestamp: 1702050463 Timestamp [UCT]: 2023-12-08 15:47:43 Age [y:d:h:m:s]: 01:105:17:46:59
Block: 908744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336715 RingCT/type: yes/0
Extra: 0159352363a01bf89d2b4113927b43622d5b97b489a42170f0648c9b8045a3c8db02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 394d4a4e40e14ad0d8b465a53d41f7dca022b3d5b7e6d9ef6ada78c9efe9f114 0.600000000000 1365799 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": 908754, "vin": [ { "gen": { "height": 908744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "394d4a4e40e14ad0d8b465a53d41f7dca022b3d5b7e6d9ef6ada78c9efe9f114" } } ], "extra": [ 1, 89, 53, 35, 99, 160, 27, 248, 157, 43, 65, 19, 146, 123, 67, 98, 45, 91, 151, 180, 137, 164, 33, 112, 240, 100, 140, 155, 128, 69, 163, 200, 219, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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