Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4e4b4ad3905a918702097d182b71a5cd0d9e99eca3dfc69b1018ab5426038e9

Tx prefix hash: 1846825cb26c06719970d99396ec59185293cdea94ab7309383de32a99d4665a
Tx public key: 1e2b06353c3a69d755476f3ae9d01e188f3ea52c432464e173077b00205fc326
Timestamp: 1627622013 Timestamp [UCT]: 2021-07-30 05:13:33 Age [y:d:h:m:s]: 03:191:18:46:02
Block: 303643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 909332 RingCT/type: yes/0
Extra: 011e2b06353c3a69d755476f3ae9d01e188f3ea52c432464e173077b00205fc32602110000001ae084ab86000000000000000000

1 output(s) for total of 60.520872157000 dcy

stealth address amount amount idx
00: e905f7e2461ef5bced087525324a1a8a0ccd7562c8c13509c3b0fa11613ed6f3 60.520872157000 633722 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": 303653, "vin": [ { "gen": { "height": 303643 } } ], "vout": [ { "amount": 60520872157, "target": { "key": "e905f7e2461ef5bced087525324a1a8a0ccd7562c8c13509c3b0fa11613ed6f3" } } ], "extra": [ 1, 30, 43, 6, 53, 60, 58, 105, 215, 85, 71, 111, 58, 233, 208, 30, 24, 143, 62, 165, 44, 67, 36, 100, 225, 115, 7, 123, 0, 32, 95, 195, 38, 2, 17, 0, 0, 0, 26, 224, 132, 171, 134, 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