Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ebbad56beec064096301c67287188db3e7d9f806e369a4ece75e2356e14a192

Tx prefix hash: 479ae193d167d4607c0ecd141408ce63d3cfffc76e80112a84df802acaa3e566
Tx public key: 61c2daf488d8e7073f568c8d91d7c511e32f2063a9d24253a8bbe7e030448b90
Timestamp: 1701059986 Timestamp [UCT]: 2023-11-27 04:39:46 Age [y:d:h:m:s]: 01:171:21:59:04
Block: 900533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384059 RingCT/type: yes/0
Extra: 0161c2daf488d8e7073f568c8d91d7c511e32f2063a9d24253a8bbe7e030448b90021100000004faf35c9c000000000000000000

1 output(s) for total of 0.637030644000 dcy

stealth address amount amount idx
00: 32be3f3e9f5863334206bead8fc8437232e32b3e192eed32e8add97c78e1a464 0.637030644000 1357040 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": 900543, "vin": [ { "gen": { "height": 900533 } } ], "vout": [ { "amount": 637030644, "target": { "key": "32be3f3e9f5863334206bead8fc8437232e32b3e192eed32e8add97c78e1a464" } } ], "extra": [ 1, 97, 194, 218, 244, 136, 216, 231, 7, 63, 86, 140, 141, 145, 215, 197, 17, 227, 47, 32, 99, 169, 210, 66, 83, 168, 187, 231, 224, 48, 68, 139, 144, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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