Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 486bf0feb267a3572253dcc7809a0fa9a3c02e8b71cb826459a2d268a3f5eb20

Tx prefix hash: f8bc55c3f5237183111215cbc37ea6eb3f6f535044cffcb760a1ddf44a6271ea
Tx public key: 8f22997240d091882b14f2cf2d8ce076bda382d3509b4fdabeb16bab9cac3707
Timestamp: 1724285065 Timestamp [UCT]: 2024-08-22 00:04:25 Age [y:d:h:m:s]: 01:079:08:50:08
Block: 1093086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315170 RingCT/type: yes/0
Extra: 018f22997240d091882b14f2cf2d8ce076bda382d3509b4fdabeb16bab9cac3707021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e802f1cf6c54351be9a6cbe94f6e28d979470cbe0e96c26f93df2cda7242b40 0.600000000000 1567959 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": 1093096, "vin": [ { "gen": { "height": 1093086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e802f1cf6c54351be9a6cbe94f6e28d979470cbe0e96c26f93df2cda7242b40" } } ], "extra": [ 1, 143, 34, 153, 114, 64, 208, 145, 136, 43, 20, 242, 207, 45, 140, 224, 118, 189, 163, 130, 211, 80, 155, 79, 218, 190, 177, 107, 171, 156, 172, 55, 7, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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