Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe5e7c11c1417c9dde46cc7b7964a9e8d09902f0b366904a1ccfd280ebf14b1

Tx prefix hash: 7e9dfc74881b116b811968a66575f3c6f866ace918c9c7c597097917cfc7ad25
Tx public key: 39499476b5e5665d60fa4d86c07ee80dbc1e06ee7f4cbeb420403994a5961661
Timestamp: 1701052106 Timestamp [UCT]: 2023-11-27 02:28:26 Age [y:d:h:m:s]: 01:054:02:44:26
Block: 900461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300026 RingCT/type: yes/0
Extra: 0139499476b5e5665d60fa4d86c07ee80dbc1e06ee7f4cbeb420403994a596166102110000000533af99f4000000000000000000

1 output(s) for total of 0.637380673000 dcy

stealth address amount amount idx
00: d01062d0ea0823f829f9a4a3048db6698586f49f340be0be0fceaae6c81b7f41 0.637380673000 1356962 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": 900471, "vin": [ { "gen": { "height": 900461 } } ], "vout": [ { "amount": 637380673, "target": { "key": "d01062d0ea0823f829f9a4a3048db6698586f49f340be0be0fceaae6c81b7f41" } } ], "extra": [ 1, 57, 73, 148, 118, 181, 229, 102, 93, 96, 250, 77, 134, 192, 126, 232, 13, 188, 30, 6, 238, 127, 76, 190, 180, 32, 64, 57, 148, 165, 150, 22, 97, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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