Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34eac33893252c2ecc6634c55466a274fb441451eb94b7e691474e1594f07b1b

Tx prefix hash: 7f846184cb4ccfb322f4633f4fd74130cf3d2bbde40c718d08d1765c685414e5
Tx public key: 673b787bbe508f876d7d0d64abc3783c247199ec35a0db9f7d16e31b0300642c
Timestamp: 1746224511 Timestamp [UCT]: 2025-05-02 22:21:51 Age [y:d:h:m:s]: 00:202:18:33:51
Block: 1274449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142630 RingCT/type: yes/0
Extra: 01673b787bbe508f876d7d0d64abc3783c247199ec35a0db9f7d16e31b0300642c0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f665e9684f6119a0b9fcaf2c93767ec68d0779e63c67b1ed70e6b6a5a7625ab 0.600000000000 1761744 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": 1274459, "vin": [ { "gen": { "height": 1274449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f665e9684f6119a0b9fcaf2c93767ec68d0779e63c67b1ed70e6b6a5a7625ab" } } ], "extra": [ 1, 103, 59, 120, 123, 190, 80, 143, 135, 109, 125, 13, 100, 171, 195, 120, 60, 36, 113, 153, 236, 53, 160, 219, 159, 125, 22, 227, 27, 3, 0, 100, 44, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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