Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff8f45a78d6420299c0ae8e1e82f30e8c49b502832492806d9466631368804d3

Tx prefix hash: 5d175984353a0f11015f8e6af0d6de067249d960dbbd6ff9aeab182ed7a38c2a
Tx public key: 4e2067e6d89708864a55b0c023469ffbf77ce86d2f4e59b205238fc430d3a66a
Timestamp: 1574555492 Timestamp [UCT]: 2019-11-24 00:31:32 Age [y:d:h:m:s]: 05:343:01:41:15
Block: 16036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1385589 RingCT/type: yes/0
Extra: 014e2067e6d89708864a55b0c023469ffbf77ce86d2f4e59b205238fc430d3a66a021100000008f95225a5000000000000000000

1 output(s) for total of 543.083937110000 dcy

stealth address amount amount idx
00: 40068aa79b76776fe3358287f52a9f6074774d20e9e43a59430f854c16bd80eb 543.083937110000 22097 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": 16046, "vin": [ { "gen": { "height": 16036 } } ], "vout": [ { "amount": 543083937110, "target": { "key": "40068aa79b76776fe3358287f52a9f6074774d20e9e43a59430f854c16bd80eb" } } ], "extra": [ 1, 78, 32, 103, 230, 216, 151, 8, 134, 74, 85, 176, 192, 35, 70, 159, 251, 247, 124, 232, 109, 47, 78, 89, 178, 5, 35, 143, 196, 48, 211, 166, 106, 2, 17, 0, 0, 0, 8, 249, 82, 37, 165, 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