Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3fd7b5bf7ac818632e841288eec046f14a8d485597d5547f3200f87ebfc555e

Tx prefix hash: aa45b9c7fb551c2c1e06e22bd5ba1202906f42d9e02c24583993f31331848b6d
Tx public key: 8cfe9fbc0d6c9c76fec52fca0d42fdfe843dcd63d9a1ea85d684aa00fb66e4ce
Timestamp: 1728606824 Timestamp [UCT]: 2024-10-11 00:33:44 Age [y:d:h:m:s]: 00:251:05:32:38
Block: 1128916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179234 RingCT/type: yes/0
Extra: 018cfe9fbc0d6c9c76fec52fca0d42fdfe843dcd63d9a1ea85d684aa00fb66e4ce02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b95fa78326c5f6eb44625cfdc2fae4f460208b3f719bc9d71e8ec3abdb2bef30 0.600000000000 1611739 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": 1128926, "vin": [ { "gen": { "height": 1128916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b95fa78326c5f6eb44625cfdc2fae4f460208b3f719bc9d71e8ec3abdb2bef30" } } ], "extra": [ 1, 140, 254, 159, 188, 13, 108, 156, 118, 254, 197, 47, 202, 13, 66, 253, 254, 132, 61, 205, 99, 217, 161, 234, 133, 214, 132, 170, 0, 251, 102, 228, 206, 2, 17, 0, 0, 0, 8, 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