Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3d6c990d5a9deffe7e6b764bd369b742adc976f01f0d01920589d3d194ec4e2

Tx prefix hash: ddbbb4a6f3d149c971bbf19fb55e8dbcfe12e3a4880973f4595b07d703b98e98
Tx public key: db9eedd30fa931ddd0f395380d652fe2c60a12154b3e8afc1d0a667fc6df3080
Timestamp: 1708888595 Timestamp [UCT]: 2024-02-25 19:16:35 Age [y:d:h:m:s]: 01:043:23:01:51
Block: 965443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292427 RingCT/type: yes/0
Extra: 01db9eedd30fa931ddd0f395380d652fe2c60a12154b3e8afc1d0a667fc6df308002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72241b6089eb1d53dc44cc18fa98f4962fb512b277953366ebc56e68f4318da5 0.600000000000 1425194 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": 965453, "vin": [ { "gen": { "height": 965443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72241b6089eb1d53dc44cc18fa98f4962fb512b277953366ebc56e68f4318da5" } } ], "extra": [ 1, 219, 158, 237, 211, 15, 169, 49, 221, 208, 243, 149, 56, 13, 101, 47, 226, 198, 10, 18, 21, 75, 62, 138, 252, 29, 10, 102, 127, 198, 223, 48, 128, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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