Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f71b57e9fb0ed544057e2a50c9d4743dba05d60aaeab16398c12689176562dd

Tx prefix hash: bf5d0fa785962100241cf51a33d06f437b1024a161db6a371b1da7b1421ca744
Tx public key: f44f3a7701ff84f049fa936f110a8f992a30aeb1e7bd2a387f332c8a5fcf92a2
Timestamp: 1657099453 Timestamp [UCT]: 2022-07-06 09:24:13 Age [y:d:h:m:s]: 02:257:10:00:11
Block: 537783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705129 RingCT/type: yes/0
Extra: 01f44f3a7701ff84f049fa936f110a8f992a30aeb1e7bd2a387f332c8a5fcf92a2021100000003faf35c9c000000000000000000

1 output(s) for total of 10.141491403000 dcy

stealth address amount amount idx
00: c3169ca22b1949dba7a52f2de558696971ada3ab07e703e472a5dc1ce75278c9 10.141491403000 967712 of 0

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": 537793, "vin": [ { "gen": { "height": 537783 } } ], "vout": [ { "amount": 10141491403, "target": { "key": "c3169ca22b1949dba7a52f2de558696971ada3ab07e703e472a5dc1ce75278c9" } } ], "extra": [ 1, 244, 79, 58, 119, 1, 255, 132, 240, 73, 250, 147, 111, 17, 10, 143, 153, 42, 48, 174, 177, 231, 189, 42, 56, 127, 51, 44, 138, 95, 207, 146, 162, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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