Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7634b72c6ab7d28306b770af8e04377b2d186cf2a5df31d9df1ad8e6114c830

Tx prefix hash: 904681acfd3a3e2108a520fc30747fbee9af247a6dc3f71d2601d32222fe3ff4
Tx public key: 3eba75b846ea4c3c63cdd895929d1a9022f83f8b7027dc211b85fc3fc136eac0
Timestamp: 1746036001 Timestamp [UCT]: 2025-04-30 18:00:01 Age [y:d:h:m:s]: 00:160:11:03:43
Block: 1272884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112334 RingCT/type: yes/0
Extra: 013eba75b846ea4c3c63cdd895929d1a9022f83f8b7027dc211b85fc3fc136eac0021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7db6eab22ea8b62a365d1a1c8fb97559786bae2508de7ff79fec5d6da2c72f0f 0.600000000000 1760161 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": 1272894, "vin": [ { "gen": { "height": 1272884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7db6eab22ea8b62a365d1a1c8fb97559786bae2508de7ff79fec5d6da2c72f0f" } } ], "extra": [ 1, 62, 186, 117, 184, 70, 234, 76, 60, 99, 205, 216, 149, 146, 157, 26, 144, 34, 248, 63, 139, 112, 39, 220, 33, 27, 133, 252, 63, 193, 54, 234, 192, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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