Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6deba969398a4c843692e6ac5ed11cd7e742366db7839dd4b8f49eae2cae35d5

Tx prefix hash: c3c80a9cdd8c35538145ed7b16b6c80224a9883e135dd7ef8c219b1eac5dcdc0
Tx public key: c50fc58e6da680e4ff2105410a1284a1ceaa0dfe10992b0a492fa26be75ba05f
Timestamp: 1700944359 Timestamp [UCT]: 2023-11-25 20:32:39 Age [y:d:h:m:s]: 01:169:21:48:25
Block: 899569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382634 RingCT/type: yes/0
Extra: 01c50fc58e6da680e4ff2105410a1284a1ceaa0dfe10992b0a492fa26be75ba05f02110000000333af99f4000000000000000000

1 output(s) for total of 0.641733126000 dcy

stealth address amount amount idx
00: 8a0bf0874a6a25999e46150949a6e5d0a448a8849b81a10600235d856e59e2c8 0.641733126000 1356028 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": 899579, "vin": [ { "gen": { "height": 899569 } } ], "vout": [ { "amount": 641733126, "target": { "key": "8a0bf0874a6a25999e46150949a6e5d0a448a8849b81a10600235d856e59e2c8" } } ], "extra": [ 1, 197, 15, 197, 142, 109, 166, 128, 228, 255, 33, 5, 65, 10, 18, 132, 161, 206, 170, 13, 254, 16, 153, 43, 10, 73, 47, 162, 107, 231, 91, 160, 95, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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