Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc19b07f2f2ba6d7f1c6a91f286099126f5502beb9c0ac345eff0f873ffb577

Tx prefix hash: 49d55e3691ed2406210dcf312abda2ec41f1ed0616c515e1f301a91bd6454b5b
Tx public key: 890068b70b3a4f98dd6170998bc19eee36f0278b32eb2fbb1640c41deaafc5df
Timestamp: 1722104460 Timestamp [UCT]: 2024-07-27 18:21:00 Age [y:d:h:m:s]: 00:302:00:10:12
Block: 1075004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215792 RingCT/type: yes/0
Extra: 01890068b70b3a4f98dd6170998bc19eee36f0278b32eb2fbb1640c41deaafc5df02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53bf567a9fe89098d3a64c4b51fab017f1f28c9a5bc89663a027ee9748ea3ef5 0.600000000000 1547523 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": 1075014, "vin": [ { "gen": { "height": 1075004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53bf567a9fe89098d3a64c4b51fab017f1f28c9a5bc89663a027ee9748ea3ef5" } } ], "extra": [ 1, 137, 0, 104, 183, 11, 58, 79, 152, 221, 97, 112, 153, 139, 193, 158, 238, 54, 240, 39, 139, 50, 235, 47, 187, 22, 64, 196, 29, 234, 175, 197, 223, 2, 17, 0, 0, 0, 10, 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