Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec78c10233a69ca2176be0868d2408cf60d48817d401b96bb2b316179d2f7092

Tx prefix hash: 035aba18c49746a67f017caeef8ddfb34b7a8f53915b4f946489e2e1f3ba5da1
Tx public key: 2e3cf915a34dc3af8f592c0da2df9953e72f30afb6bea20127f1ecfc6a1ce1fd
Timestamp: 1669859064 Timestamp [UCT]: 2022-12-01 01:44:24 Age [y:d:h:m:s]: 02:057:08:17:17
Block: 642776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562861 RingCT/type: yes/0
Extra: 012e3cf915a34dc3af8f592c0da2df9953e72f30afb6bea20127f1ecfc6a1ce1fd021100000005e6d27f9c000000000000000000

1 output(s) for total of 4.552147022000 dcy

stealth address amount amount idx
00: 989467db238a95a4d84cc02b92468e8265cd022d7a3ecc9e2f12b65c2dfb9a02 4.552147022000 1082685 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": 642786, "vin": [ { "gen": { "height": 642776 } } ], "vout": [ { "amount": 4552147022, "target": { "key": "989467db238a95a4d84cc02b92468e8265cd022d7a3ecc9e2f12b65c2dfb9a02" } } ], "extra": [ 1, 46, 60, 249, 21, 163, 77, 195, 175, 143, 89, 44, 13, 162, 223, 153, 83, 231, 47, 48, 175, 182, 190, 162, 1, 39, 241, 236, 252, 106, 28, 225, 253, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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