Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f614f0c0c6f81a548cdfe1d92a510da3f6f7b40ab17fdfa9fa439a6419211006

Tx prefix hash: 20c69eff85bd9f16cd010ec4f54e3830f36d98d5992d230518d6aa7ba2465d59
Tx public key: cf7c308a9c2d01abb5af411c7d5058578838c22471f6629ad4f1a16a322ce55e
Timestamp: 1723277630 Timestamp [UCT]: 2024-08-10 08:13:50 Age [y:d:h:m:s]: 01:153:09:40:10
Block: 1084734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368199 RingCT/type: yes/0
Extra: 01cf7c308a9c2d01abb5af411c7d5058578838c22471f6629ad4f1a16a322ce55e02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65bda799008fd9ea9097ccf62ffba99901ca7c6b22c59ca9247d8b46636b5f60 0.600000000000 1559113 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": 1084744, "vin": [ { "gen": { "height": 1084734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65bda799008fd9ea9097ccf62ffba99901ca7c6b22c59ca9247d8b46636b5f60" } } ], "extra": [ 1, 207, 124, 48, 138, 156, 45, 1, 171, 181, 175, 65, 28, 125, 80, 88, 87, 136, 56, 194, 36, 113, 246, 98, 154, 212, 241, 161, 106, 50, 44, 229, 94, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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