Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2e963ebcdcf112aba48add69b063ed7064cc4cd8a4ffd78c4b14de8edd4cce6

Tx prefix hash: a41f11ffc8169f5180d1541ae0481911cf89e1b892033c55b47426fee74b77f1
Tx public key: 8ada43e4c52e3179a409a7489301861f4f7b6c1b5870b0fc04935df37cc821df
Timestamp: 1739523647 Timestamp [UCT]: 2025-02-14 09:00:47 Age [y:d:h:m:s]: 00:081:22:49:20
Block: 1218980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58613 RingCT/type: yes/0
Extra: 018ada43e4c52e3179a409a7489301861f4f7b6c1b5870b0fc04935df37cc821df02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5252f1512e291fbab378480a26efd6869e17ce31826800e15ec1687c58565e7 0.600000000000 1705801 of 15

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": 1218990, "vin": [ { "gen": { "height": 1218980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5252f1512e291fbab378480a26efd6869e17ce31826800e15ec1687c58565e7" } } ], "extra": [ 1, 138, 218, 67, 228, 197, 46, 49, 121, 164, 9, 167, 72, 147, 1, 134, 31, 79, 123, 108, 27, 88, 112, 176, 252, 4, 147, 93, 243, 124, 200, 33, 223, 2, 17, 0, 0, 0, 13, 31, 10, 83, 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