Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 542a50bb518949b3455edc9120b21d190674fa727a2ec0952271fd2701ecee54

Tx prefix hash: 0ed274097ec1167493079799fb46cd1f5cae567871530b266da7a6c26617613e
Tx public key: 8dd4dfb20817b547f2f53b09e95b09b02bc79ef7e420b23aee89e478816a39fd
Timestamp: 1698728187 Timestamp [UCT]: 2023-10-31 04:56:27 Age [y:d:h:m:s]: 01:229:07:59:48
Block: 881405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424846 RingCT/type: yes/0
Extra: 018dd4dfb20817b547f2f53b09e95b09b02bc79ef7e420b23aee89e478816a39fd02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.737121972000 dcy

stealth address amount amount idx
00: f80942ff9eedca2c4ca7359c4882cfe8fbb9f69aec4722a5512d10e1f45272c7 0.737121972000 1336989 of 0

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": 881415, "vin": [ { "gen": { "height": 881405 } } ], "vout": [ { "amount": 737121972, "target": { "key": "f80942ff9eedca2c4ca7359c4882cfe8fbb9f69aec4722a5512d10e1f45272c7" } } ], "extra": [ 1, 141, 212, 223, 178, 8, 23, 181, 71, 242, 245, 59, 9, 233, 91, 9, 176, 43, 199, 158, 247, 228, 32, 178, 58, 238, 137, 228, 120, 129, 106, 57, 253, 2, 17, 0, 0, 0, 3, 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