Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779058b3eeb0ebb0d5decdaef4dbce689e77456df4cb5fa6f0386ba3369a32ef

Tx prefix hash: 1fbe537763e8efcc522d261c3c511c2dc1bf8d295256b0cb81df20bd03e6fc22
Tx public key: 1f28172a89f88f57c0359fb917c7305e5cb3fc53472104b7fbfdf57cfc46d62b
Timestamp: 1717012991 Timestamp [UCT]: 2024-05-29 20:03:11 Age [y:d:h:m:s]: 00:293:15:36:56
Block: 1032797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209879 RingCT/type: yes/0
Extra: 011f28172a89f88f57c0359fb917c7305e5cb3fc53472104b7fbfdf57cfc46d62b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cd9a61adc8151bf545219868092731f2be874fb84035bcca58f4c37aa5bf002 0.600000000000 1501252 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": 1032807, "vin": [ { "gen": { "height": 1032797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cd9a61adc8151bf545219868092731f2be874fb84035bcca58f4c37aa5bf002" } } ], "extra": [ 1, 31, 40, 23, 42, 137, 248, 143, 87, 192, 53, 159, 185, 23, 199, 48, 94, 92, 179, 252, 83, 71, 33, 4, 183, 251, 253, 245, 124, 252, 70, 214, 43, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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