Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 051d703479564bee57fcc239c096de1d65e905f030d05ffc91582e1d54ad8f7a

Tx prefix hash: 3fc3b72c48b1676d0889d20fb67d60abafaadbb4425ccfc6d0f2f3074e35cc60
Tx public key: b47ddb2c7031c54a2dcdc5bdcd60f3f2d48fa42d63ce7aaa1412a26e8ecae567
Timestamp: 1734457946 Timestamp [UCT]: 2024-12-17 17:52:26 Age [y:d:h:m:s]: 00:094:14:33:04
Block: 1177336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67371 RingCT/type: yes/0
Extra: 01b47ddb2c7031c54a2dcdc5bdcd60f3f2d48fa42d63ce7aaa1412a26e8ecae5670211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e791cf764ca133400c9b9c9590fd89676f30cf619ea344c8ee8c19e3636fc5e 0.600000000000 1663707 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": 1177346, "vin": [ { "gen": { "height": 1177336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e791cf764ca133400c9b9c9590fd89676f30cf619ea344c8ee8c19e3636fc5e" } } ], "extra": [ 1, 180, 125, 219, 44, 112, 49, 197, 74, 45, 205, 197, 189, 205, 96, 243, 242, 212, 143, 164, 45, 99, 206, 122, 170, 20, 18, 162, 110, 142, 202, 229, 103, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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