Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a0e7ef7b2cea438c5789ff99bee9385cdc55700e7badf59c1fa8225a0ea7208

Tx prefix hash: 27475dedca9601503fc9909741b1a2bf6f2c26eece769a0f6474a1f8f46c27e9
Tx public key: 6f359206ab9ea9e99a5b1142c0bf8dd607dce885ba03f2310b27f71c985d469d
Timestamp: 1673242508 Timestamp [UCT]: 2023-01-09 05:35:08 Age [y:d:h:m:s]: 02:079:08:05:21
Block: 670765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 578389 RingCT/type: yes/0
Extra: 016f359206ab9ea9e99a5b1142c0bf8dd607dce885ba03f2310b27f71c985d469d02110000000352542ceb000000000000000000

1 output(s) for total of 3.676859740000 dcy

stealth address amount amount idx
00: 0a764a7b6d221a1dcc2fab9e3f78f531cf0cbd4f799a2d185ee8742abd30bd31 3.676859740000 1112184 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": 670775, "vin": [ { "gen": { "height": 670765 } } ], "vout": [ { "amount": 3676859740, "target": { "key": "0a764a7b6d221a1dcc2fab9e3f78f531cf0cbd4f799a2d185ee8742abd30bd31" } } ], "extra": [ 1, 111, 53, 146, 6, 171, 158, 169, 233, 154, 91, 17, 66, 192, 191, 141, 214, 7, 220, 232, 133, 186, 3, 242, 49, 11, 39, 247, 28, 152, 93, 70, 157, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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