Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44458609a36d3023f265d3f613cbd742b50f6899354c213eba9e16e3e3de6cf1

Tx prefix hash: c27d72562b51e7a01e6f5ad57d6ba9228b3b27fa4aff5a8c7e44732d27d5ea0f
Tx public key: ea38e8c834769a5c6fe0d618a0b9283e6d7fea5133344970f8b98a170a1ba8b8
Timestamp: 1745870228 Timestamp [UCT]: 2025-04-28 19:57:08 Age [y:d:h:m:s]: 00:205:18:33:01
Block: 1271520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144768 RingCT/type: yes/0
Extra: 01ea38e8c834769a5c6fe0d618a0b9283e6d7fea5133344970f8b98a170a1ba8b802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97a044f5000bf853f0a90337508ec4c3b20cb9f228830ca2dd4266de880a4d3d 0.600000000000 1758783 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": 1271530, "vin": [ { "gen": { "height": 1271520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97a044f5000bf853f0a90337508ec4c3b20cb9f228830ca2dd4266de880a4d3d" } } ], "extra": [ 1, 234, 56, 232, 200, 52, 118, 154, 92, 111, 224, 214, 24, 160, 185, 40, 62, 109, 127, 234, 81, 51, 52, 73, 112, 248, 185, 138, 23, 10, 27, 168, 184, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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