Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f56e13e48d8c134ba3eefd00a8e170e79c128908d2ccad9a77740c33327a530

Tx prefix hash: b4e68ca2a7efd03f4a72f6d1c083684f7ee53174a241795a19d55d14357e573f
Tx public key: 270524417b3345d4957f997906b6e74ce7e20f3b972442bb7ab2bcb50ceb0da9
Timestamp: 1755776503 Timestamp [UCT]: 2025-08-21 11:41:43 Age [y:d:h:m:s]: 00:090:15:51:54
Block: 1351249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64726 RingCT/type: yes/0
Extra: 01270524417b3345d4957f997906b6e74ce7e20f3b972442bb7ab2bcb50ceb0da902110000000bad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a746d23f86c579bad06f1cbc8b806c19ec3fbdf78072d0f62544cc1a3b7baaa 0.600000000000 1839200 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": 1351259, "vin": [ { "gen": { "height": 1351249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a746d23f86c579bad06f1cbc8b806c19ec3fbdf78072d0f62544cc1a3b7baaa" } } ], "extra": [ 1, 39, 5, 36, 65, 123, 51, 69, 212, 149, 127, 153, 121, 6, 182, 231, 76, 231, 226, 15, 59, 151, 36, 66, 187, 122, 178, 188, 181, 12, 235, 13, 169, 2, 17, 0, 0, 0, 11, 173, 121, 72, 208, 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