Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0ef9a208f1d92e80e5c4d8fc57141c60f3adf326410d7241fe184c3b80f5b6a

Tx prefix hash: b9454965ed8a1e4b81c654540fd6b5019715872d733dac504833c3668a80da58
Tx public key: e25333e1751f90da1dbd655d02fb439e6489f805293b8d3c597d35d4077d5274
Timestamp: 1670332291 Timestamp [UCT]: 2022-12-06 13:11:31 Age [y:d:h:m:s]: 02:141:14:14:09
Block: 646678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622911 RingCT/type: yes/0
Extra: 01e25333e1751f90da1dbd655d02fb439e6489f805293b8d3c597d35d4077d527402110000000275e3f0e9000000000000000000

1 output(s) for total of 4.418626864000 dcy

stealth address amount amount idx
00: 415017117e005db420f2e2939f16c9e76bab0dc278c15a6839642304185f7e4a 4.418626864000 1086913 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": 646688, "vin": [ { "gen": { "height": 646678 } } ], "vout": [ { "amount": 4418626864, "target": { "key": "415017117e005db420f2e2939f16c9e76bab0dc278c15a6839642304185f7e4a" } } ], "extra": [ 1, 226, 83, 51, 225, 117, 31, 144, 218, 29, 189, 101, 93, 2, 251, 67, 158, 100, 137, 248, 5, 41, 59, 141, 60, 89, 125, 53, 212, 7, 125, 82, 116, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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