Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 494ed01d36eb4d4049b65204e2ca92c7ef47ef2738667ba702853104b4dc7292

Tx prefix hash: 74ca16e848e76a9765f607f0ec6d77784ae265a23e6e37c2908ed8e2416e3341
Tx public key: 068e5c5011dfc2db479dddf32aed0ba892e1e0b0be13cd4d500a61bb8a59dcb1
Timestamp: 1703426552 Timestamp [UCT]: 2023-12-24 14:02:32 Age [y:d:h:m:s]: 01:182:01:14:44
Block: 920153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391046 RingCT/type: yes/0
Extra: 01068e5c5011dfc2db479dddf32aed0ba892e1e0b0be13cd4d500a61bb8a59dcb102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5d43930dd2bfa58411a28fd9d6d60c07d5c5c2e7089716c42c171013e682984 0.600000000000 1377831 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": 920163, "vin": [ { "gen": { "height": 920153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5d43930dd2bfa58411a28fd9d6d60c07d5c5c2e7089716c42c171013e682984" } } ], "extra": [ 1, 6, 142, 92, 80, 17, 223, 194, 219, 71, 157, 221, 243, 42, 237, 11, 168, 146, 225, 224, 176, 190, 19, 205, 77, 80, 10, 97, 187, 138, 89, 220, 177, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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