Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cecc6ba862ebb51132ad62fb557f11c261ff78bd5b9d9c96afca5d5dd0389cfc

Tx prefix hash: dbbe6308b5152889dd6f450d5135d0b2a82f42f76e5f3b821bca6d0278edcb38
Tx public key: dd7b121e9172de1cfa8676d433463807fc52d1b0e8c3b6493ffa4a8cd60c3341
Timestamp: 1749153128 Timestamp [UCT]: 2025-06-05 19:52:08 Age [y:d:h:m:s]: 00:167:12:09:21
Block: 1298691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117414 RingCT/type: yes/0
Extra: 01dd7b121e9172de1cfa8676d433463807fc52d1b0e8c3b6493ffa4a8cd60c3341021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4280c67d6faeea052af60fd2de1a5785d9c631caf4510efd6cc061095f341d74 0.600000000000 1786220 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": 1298701, "vin": [ { "gen": { "height": 1298691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4280c67d6faeea052af60fd2de1a5785d9c631caf4510efd6cc061095f341d74" } } ], "extra": [ 1, 221, 123, 18, 30, 145, 114, 222, 28, 250, 134, 118, 212, 51, 70, 56, 7, 252, 82, 209, 176, 232, 195, 182, 73, 63, 250, 74, 140, 214, 12, 51, 65, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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