Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ce4fae464feaff96b1447cf73342be12c99f6b4d13adb0e27087e240d7379ff

Tx prefix hash: e5257b4b06029ba2d684edd6e395717bf0b3a352a1d1b541b146c1ae35c54608
Tx public key: 35e36dbc9f0fb77d37229e2a24b4231feadbf8adf7198a249c6e2791f03c374e
Timestamp: 1728553901 Timestamp [UCT]: 2024-10-10 09:51:41 Age [y:d:h:m:s]: 00:168:22:56:40
Block: 1128473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120532 RingCT/type: yes/0
Extra: 0135e36dbc9f0fb77d37229e2a24b4231feadbf8adf7198a249c6e2791f03c374e021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ebeb6e9a110fac65de472871c9f9acb722abdfb39e89b862933a20401ebef44 0.600000000000 1611292 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": 1128483, "vin": [ { "gen": { "height": 1128473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ebeb6e9a110fac65de472871c9f9acb722abdfb39e89b862933a20401ebef44" } } ], "extra": [ 1, 53, 227, 109, 188, 159, 15, 183, 125, 55, 34, 158, 42, 36, 180, 35, 31, 234, 219, 248, 173, 247, 25, 138, 36, 156, 110, 39, 145, 240, 60, 55, 78, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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