Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de3c1a1c2ce01dd491ad39d85995ce479d4cfe03e5508e8d6176d6fd3c7971d3

Tx prefix hash: 809c79a4eadc0cebad074756c091dab47e9d4e3655941d986f7d844b9a2f79bf
Tx public key: 457de6e7a9f544b7486d23667e960fc79fd6e094f32a3ace9e1c1d29488440ad
Timestamp: 1706515176 Timestamp [UCT]: 2024-01-29 07:59:36 Age [y:d:h:m:s]: 01:073:05:49:41
Block: 945735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313442 RingCT/type: yes/0
Extra: 01457de6e7a9f544b7486d23667e960fc79fd6e094f32a3ace9e1c1d29488440ad02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14539b53f969cc9124af6b7c0cfb99cdbd346161a7a9910b934c5fe1bb30cf2e 0.600000000000 1404053 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": 945745, "vin": [ { "gen": { "height": 945735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14539b53f969cc9124af6b7c0cfb99cdbd346161a7a9910b934c5fe1bb30cf2e" } } ], "extra": [ 1, 69, 125, 230, 231, 169, 245, 68, 183, 72, 109, 35, 102, 126, 150, 15, 199, 159, 214, 224, 148, 243, 42, 58, 206, 158, 28, 29, 41, 72, 132, 64, 173, 2, 17, 0, 0, 0, 3, 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