Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebec5c93b43baa40a3567a976b5e1d378abde38931875418038a6b89c8b1ea68

Tx prefix hash: 2d6faebe4bf07f166b5f4b617447bc88c05872cf8867b7c9b7e19320bd6efc7d
Tx public key: 684123e76acf10f62078e038857feaab9dae568c1c07196dfa88a7317043281f
Timestamp: 1677510465 Timestamp [UCT]: 2023-02-27 15:07:45 Age [y:d:h:m:s]: 02:059:17:32:34
Block: 706180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564282 RingCT/type: yes/0
Extra: 01684123e76acf10f62078e038857feaab9dae568c1c07196dfa88a7317043281f021100000002835e4d22000000000000000000

1 output(s) for total of 2.806289136000 dcy

stealth address amount amount idx
00: 9312c1fd817a0014c570d159db40216911a62d8b4a8acb27f4a8e115f4998a66 2.806289136000 1149905 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": 706190, "vin": [ { "gen": { "height": 706180 } } ], "vout": [ { "amount": 2806289136, "target": { "key": "9312c1fd817a0014c570d159db40216911a62d8b4a8acb27f4a8e115f4998a66" } } ], "extra": [ 1, 104, 65, 35, 231, 106, 207, 16, 246, 32, 120, 224, 56, 133, 127, 234, 171, 157, 174, 86, 140, 28, 7, 25, 109, 250, 136, 167, 49, 112, 67, 40, 31, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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