Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0dfca5ef0c9074797464d2b896c7180453426d56c482c7c20b1776e22f9fed

Tx prefix hash: ddbb844ef95a0947ec0664514c9ad0f930389285c98da24ce841dea53f7fb01c
Tx public key: 4b67cabc0c80e08a2b95c6bbcf944941c9d9beecea2e49b3c8c2d04daef12325
Timestamp: 1731976600 Timestamp [UCT]: 2024-11-19 00:36:40 Age [y:d:h:m:s]: 00:151:08:31:05
Block: 1156759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107994 RingCT/type: yes/0
Extra: 014b67cabc0c80e08a2b95c6bbcf944941c9d9beecea2e49b3c8c2d04daef12325021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 739aeb55216bffcae7e9f702e84146231fda5ff89b2dd4b79f1be4ee02628f5b 0.600000000000 1642382 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": 1156769, "vin": [ { "gen": { "height": 1156759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "739aeb55216bffcae7e9f702e84146231fda5ff89b2dd4b79f1be4ee02628f5b" } } ], "extra": [ 1, 75, 103, 202, 188, 12, 128, 224, 138, 43, 149, 198, 187, 207, 148, 73, 65, 201, 217, 190, 236, 234, 46, 73, 179, 200, 194, 208, 77, 174, 241, 35, 37, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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