Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb5685313cf38b7e002ea01048cb29d03e9a4d9bf062f6bd944a278b1b9172f4

Tx prefix hash: 563946766cf67d0807180cd6c0e4826c89c073f09a936c553a3af38cdd72a5f2
Tx public key: 4a779621a61841a2446268a2d9d76602a99b929fae69119ef2c7b199d883eb1a
Timestamp: 1700797141 Timestamp [UCT]: 2023-11-24 03:39:01 Age [y:d:h:m:s]: 01:056:20:38:18
Block: 898348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302005 RingCT/type: yes/0
Extra: 014a779621a61841a2446268a2d9d76602a99b929fae69119ef2c7b199d883eb1a021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.647739139000 dcy

stealth address amount amount idx
00: 60fefb78f4698ee6bd9f8bf5d9f29035868404d81b0a8e9db352f04ec6459ee1 0.647739139000 1354761 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": 898358, "vin": [ { "gen": { "height": 898348 } } ], "vout": [ { "amount": 647739139, "target": { "key": "60fefb78f4698ee6bd9f8bf5d9f29035868404d81b0a8e9db352f04ec6459ee1" } } ], "extra": [ 1, 74, 119, 150, 33, 166, 24, 65, 162, 68, 98, 104, 162, 217, 215, 102, 2, 169, 155, 146, 159, 174, 105, 17, 158, 242, 199, 177, 153, 216, 131, 235, 26, 2, 17, 0, 0, 0, 6, 230, 210, 127, 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